date:20190131

** 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: bug 1811857 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 11:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 3.13.0-165.215 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu 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: bug 1811857 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 11:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker

** 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: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-142.168 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1813779
  phase: Testing
  phase-changed: Monday, 28. January 2019 12:58 UTC
  reason:
-   certification-testing: Ongoing -- testing in progress
+   promote-to-security: Holding -- cycle not ready to release
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux-oem: 4.15.0-1032.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1813779
  phase: Testing
  phase-changed: Monday, 28. January 2019 12:58 UTC
  reason:
promote-to-security: Holding -- cycle not ready to release
promote-to-updates: Holding -- cycle not ready to release

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

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

[Kernel-packages] [Bug 1813683] Re: linux-image-4.15.0-44-generic tty login not work

2019-01-31 Thread Ulli Horlacher

See https://bugs.launchpad.net/bugs/1812095

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

Title:
  linux-image-4.15.0-44-generic tty login not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just updated my ubuntu 18.04 and received the linux-
  image-4.15.0-44-generic.

  After update and reboot the machine, my computer starts normally.

  Seems boot normally

  but when gets to the login screen (I'm not use any kind of graphical
  login manager, boot pure on console/text)

  I just need to press enter (doesn't matter if type my login or not),
  then starts a loop, like if my 'enter' key has some kind of mechanical
  defect.

  Keeps pressing 'enter' until I do a CTRL-C.

  If I press enter key again, starts all over again. Periodically
  pressing 'enter' key in lapse of seconds.

  To prevent, I just had to boot using linux-image-4.15.0-43-generic and
  could login normally.

  What can I provide to you look this? I think it's my first time here
  or one of firsts

  Thanks in advanced.

  Regards

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

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

[Kernel-packages] [Bug 1770271] Re: VegaM support

2019-01-31 Thread Timo Aaltonen

bionic has 18.2.2 now

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

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

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

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

[Kernel-packages] [Bug 1798776] Re: kvm_stat : missing python dependency

2019-01-31 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  kvm_stat : missing python dependency

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  After installing linux-tools-host, the included kvm_stat utility won't
  work:

  root@ubuntu:~# kvm_stat 
  -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or 
directory

  Reason is that there is apparently no dependency on a python package
  from the linux-tools-host package.

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

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

[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -proposed tracker

2019-01-31 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-165.215
/trusty-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  linux: 3.13.0-165.215 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu 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: bug 1811857 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 11:49 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker

2019-01-31 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.15.0-1032.37/oem-4.15-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.15.0-1032.37 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  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: 1813779
  phase: Testing
  phase-changed: Monday, 28. January 2019 12:58 UTC
  reason:
certification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker

2019-01-31 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-142.168
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  linux: 4.4.0-142.168 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial)
  derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 
(linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1812359] Re: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

We don't need any more logs as this bug is fully understood.

Although it sounds like you might now be experiencing bug 1795760. Also
there are other related bugs to that like bug 1790525 or bug 1795774.
Plus there is the original bug 1727356. Those last three are all fixed
in 19.04 so please don't use 18.04 any more - it doesn't have enough
fixes for your hardware.

The other bug you are experiencing is bug 1760849. So the unresolved
bugs you are experiencing in 19.04 are bug 1812359, bug 1760849 and
maybe 1795760.

But to avoid confusion we should really only talk about bug 1812359
here. And you should only use Ubuntu 19.04 because 18.04 contains a
little too many of those bugs.

If you would like to speed up the resolution of this problem (bug
1812359) then please follow the steps in comment #81.

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

Title:
  No login screen displayed on a NETBOX nT-435/535 (kernel reports an
  LVDS output which does not exist as connected and on)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a machine with only one display (VGA), the kernel is reporting two:

  grep . /sys/class/drm/*/enabled

 /sys/class/drm/card0-LVDS-1/enabled:enabled
 /sys/class/drm/card0-VGA-1/enabled:enabled

  ls /sys/class/drm

 card0 card0-LVDS-1 card0-VGA-1 renderD128 version

  grep . /sys/class/drm/*/dpms

 /sys/class/drm/card0-LVDS-1/dpms:On
 /sys/class/drm/card0-VGA-1/dpms:On

  which then triggers bug 1760849 and the login screen is never visible.

  ---

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1721987] Re: No sound from right audio channel

2019-01-31 Thread Reda Borchardt

Ok, I got it working without needing to recompile the kernel. Make sure
that you have the alsa-tools installed on your machine. Running the
attached script at runtime will send the necessary verbs to the sound
card to enable the right speaker.

Here is my systemd service file to launch it at startup. (Type idle is
important to launch it at the end)

[Unit]
Description=Huawei-soundfix

[Service]
Type=idle
ExecStart=/usr/bin/bash /usr/bin/huawei-sound.sh

[Install]
WantedBy=multi-user.target
~

** Attachment added: "huawei-sound.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721987/+attachment/5234959/+files/huawei-sound.sh

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

Title:
  No sound from right audio channel

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

Bug description:
  No audio comes out of the right speaker on the laptop.  When playing a
  test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
  right-channel audio is never heard (i.e., it does not get converted
  into mono and played through the left speaker).

  When plugging in headphones, audio is heard from both channels.

  In Windows, both speakers work, so it is not a physical problem with
  the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 12:58:01 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HUAWEI HUAWEI MateBook X
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: HUAWEI MateBook X
  dmi.board.vendor: HUAWEI
  dmi.board.version: 2.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr:
  dmi.product.family: HUAWEI MateBook
  dmi.product.name: HUAWEI MateBook X
  dmi.product.version: 2.0
  dmi.sys.vendor: HUAWEI

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

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

[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel

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

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

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

Title:
  Fix non-working pinctrl-intel

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Intel pinctrl doesn't work.
  There's a WWAN card needs to use pinctrl to reset itself after firmware 
update. Currently we can't use pinctrl to reset it.

  [Fix]
  Translate GPIO to pinctrl pins correctly.

  [Test]
  The WWAN reset function works once the fix is applied.

  [Regression Potential]
  Low. Limits to pinctrl-intel and it's in mainline for a while.

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

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

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

2019-01-31 Thread Kai-Heng Feng

** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Released
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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

[Kernel-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

This bug was fixed in the package kmod - 24-1ubuntu3.2

---
kmod (24-1ubuntu3.2) bionic; urgency=medium

  * Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions.
(LP: #1802689, #1802135)

 -- Michael Hudson-Doyle   Tue, 13 Nov 2018
10:54:37 +1300

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Kernel-packages] [Bug 1802135] Update Released

2019-01-31 Thread Adam Conrad

The verification of the Stable Release Update for kmod has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Kernel-packages] [Bug 1812359] Re: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

2019-01-31 Thread d a i s y

Okay thanks,

Here I found something new in Ubuntu 18.04.2,
I thought about to install kernel 4.15.0-43, login screen appeared but 
resolution issue and not network adapter, neither ethernet nor wireless, so 
just leave it

Then for kernel 4.15.0-45-generic, I've disabled wayland
During booting, ubuntu logo appeared (seems like when we set nomodeset), then 
splash divided into two(ubuntu logo left and right side) and after a minute 
login screen appeared,

but after login, just a wallpaper and nothing like it's freezing, same
issue.

Please check a log if you can find something new.

** Attachment added: "journalctl -b-1 > 18.04.2_boot_4.15.0-45.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+attachment/5234958/+files/18.04.2_boot_4.15.0-45.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/1812359

Title:
  No login screen displayed on a NETBOX nT-435/535 (kernel reports an
  LVDS output which does not exist as connected and on)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a machine with only one display (VGA), the kernel is reporting two:

  grep . /sys/class/drm/*/enabled

 /sys/class/drm/card0-LVDS-1/enabled:enabled
 /sys/class/drm/card0-VGA-1/enabled:enabled

  ls /sys/class/drm

 card0 card0-LVDS-1 card0-VGA-1 renderD128 version

  grep . /sys/class/drm/*/dpms

 /sys/class/drm/card0-LVDS-1/dpms:On
 /sys/class/drm/card0-VGA-1/dpms:On

  which then triggers bug 1760849 and the login screen is never visible.

  ---

  $ dpkg -s mutter
  Package: mutter
  Status: install ok installed
  Priority: optional
  Section: x11
  Installed-Size: 101
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.3-2~ubuntu18.04.2
  Provides: x-window-manager
  Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), 
libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 
3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 
3.21.4), zenity
  Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs
  Description: lightweight GTK+ window manager
   Mutter is a small window manager, using GTK+ and Clutter to do
   everything.
   .
   Mutter is the clutter-based evolution of Metacity, which, as the
   author says, is a "Boring window manager for the adult in you. Many
   window managers are like Marshmallow Froot Loops; Metacity is like
   Cheerios."
   .
   This package contains the core binaries.
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mutter 3.28.3-2~ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 15:02:22 2019
  InstallationDate: Installed on 2019-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot

This bug was fixed in the package kmod - 24-1ubuntu3.2

---
kmod (24-1ubuntu3.2) bionic; urgency=medium

  * Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions.
(LP: #1802689, #1802135)

 -- Michael Hudson-Doyle   Tue, 13 Nov 2018
10:54:37 +1300

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

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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

[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

This bug was fixed in the package thermald - 1.7.0-5ubuntu2

---
thermald (1.7.0-5ubuntu2) bionic; urgency=medium

  * Honor ACPI _CRT for processor thermal zone (LP: #1803360)
There are some new fanless platforms use DPTF's virtual sensor
instead of INT340X devices. Because of that, the _PSV is no
longer in use, at least not directly, hence its value may set
higher then _CRT. To a fanless system that means no cooling
device gets activated before _CRT, so the system will be
considered overheated by Linux kernel, and gets shutdown by the
kernel.  Upstream fixes:
 - 7af3eef07dc7 Ignore _TRT and B0D4 device if passive 1 UUID not present
   (prerequisite)
 - 97976782dd26 Honor ACPI _CRT for processor thermal zone

 -- Colin King   Mon, 14 Jan 2019 23:29:41
+

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

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Released
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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

[Kernel-packages] [Bug 1803360] Update Released

2019-01-31 Thread Adam Conrad

The verification of the Stable Release Update for thermald has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Released
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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

[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module

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

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

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

Title:
  kernel oops in bcache module

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

Bug description:
  SRU Justification
  =

  [Impact]

  Some users see panics like the following when performing fstrim on a
  bcached volume:

  [  529.803060] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [  530.183928] #PF error: [normal kernel read fault]
  [  530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0
  [  530.750887] Oops:  [#1] SMP PTI
  [  530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 
5.0.0-rc1+ #3
  [  531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 12/27/2015
  [  531.693137] RIP: 0010:blk_queue_split+0x148/0x620
  [  531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 
85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 
44 8b 56 0c 48
  8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3
  [  532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246
  [  533.093571] RAX:  RBX: 00046000 RCX: 

  [  533.441865] RDX: 0200 RSI:  RDI: 

  [  533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: 

  [  534.137512] R10: b9b708df3958 R11:  R12: 

  [  534.485329] R13:  R14:  R15: 
940d39212020
  [  534.833319] FS:  7efec26e3840() GS:940d1f48() 
knlGS:
  [  535.224098] CS:  0010 DS:  ES:  CR0: 80050033
  [  535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 
001606e0
  [  535.851759] Call Trace:
  [  535.970308]  ? mempool_alloc_slab+0x15/0x20
  [  536.174152]  ? bch_data_insert+0x42/0xd0 [bcache]
  [  536.403399]  blk_mq_make_request+0x97/0x4f0
  [  536.607036]  generic_make_request+0x1e2/0x410
  [  536.819164]  submit_bio+0x73/0x150
  [  536.980168]  ? submit_bio+0x73/0x150
  [  537.149731]  ? bio_associate_blkg_from_css+0x3b/0x60
  [  537.391595]  ? _cond_resched+0x1a/0x50
  [  537.573774]  submit_bio_wait+0x59/0x90
  [  537.756105]  blkdev_issue_discard+0x80/0xd0
  [  537.959590]  ext4_trim_fs+0x4a9/0x9e0
  [  538.137636]  ? ext4_trim_fs+0x4a9/0x9e0
  [  538.324087]  ext4_ioctl+0xea4/0x1530
  [  538.497712]  ? _copy_to_user+0x2a/0x40
  [  538.679632]  do_vfs_ioctl+0xa6/0x600
  [  538.853127]  ? __do_sys_newfstat+0x44/0x70
  [  539.051951]  ksys_ioctl+0x6d/0x80
  [  539.212785]  __x64_sys_ioctl+0x1a/0x20
  [  539.394918]  do_syscall_64+0x5a/0x110
  [  539.568674]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  Under certain conditions, the test for whether an operation should be
  written back to the underlying device was incorrect. Specifically, in
  should_writeback(), we were hitting a case where an optimisation for
  partial stripe conditions was returning true and so should_writeback()
  was returning true early. This caused the code to go down an incorrect
  path and create bios that contained NULL pointers.

  To fix this issue, make sure that should_writeback() on a discard op
  never returns true.

  
  [Test Case]

  We have observed it on some systems where both:
  1) LVM/devmapper is involved (bcache backing device is LVM volume) and
  2) writeback cache is involved (bcache cache_mode is writeback)

  Not every machine exhibits the bug. On one machine that does exhibit
  the bug, we can reliably reproduce it with:

   # echo writeback > /sys/block/bcache0/bcache/cache_mode
   # mount /dev/bcache0 /test
   # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero 
of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test

  
  [Regression Potential]

  This could affect any device where bcache is used.

  In mitigation, however: the patch is simple, is limited to considering
  discard operations. The patch has been accepted upstream [1] and the
  maintainer will be including it in SuSE kernels [2]. A Gentoo user
  validated the upstream patch independently [3].

  
  [1] https://www.spinics.net/lists/linux-bcache/msg06997.html
  [2] https://www.spinics.net/lists/linux-bcache/msg06998.html
  [3] https://bugzilla.kernel.org/show_bug.cgi?id=196103#c3

  
  [Original Description]

  This was on an 18.04.1 install running the 4.15-34 generic kernel image, 
running from a normal ext4 root device.
  I had just a short while before created a new bcache device that was mounted 
but to which no data had been written yet. Then without any

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

This bug was fixed in the package libdrm - 2.4.95-1~18.04.1

---
libdrm (2.4.95-1~18.04.1) bionic; urgency=medium

  * Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597)

libdrm (2.4.95-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * rules, control: Switch to meson.

  [ Andreas Boll ]
  * New upstream release.
- Fixes WebGL on Firefox (Closes: #907698).
  * Update libdrm-amdgpu1.symbols and shlibs.
  * Drop static libdrm library from libdrm-dev.
  * Update extend-diff-ignore.

libdrm (2.4.94-1) unstable; urgency=medium

  [ Guido Günther ]
  * Enable etnaviv on arm64 (Closes: #906915)

  [ Timo Aaltonen ]
  * New upstream release. (LP: #1789924)
  * Update libdrm-amdgpu1.symbols and shlibs.

libdrm (2.4.93-1) unstable; urgency=medium

  * New upstream release.
  * Update libdrm-freedreno1.symbols and shlibs.

libdrm (2.4.92-1) unstable; urgency=medium

  * New upstream release.
  * Update libdrm-freedreno1.symbols and shlibs.
  * control: Update to my Debian address.
  * Update Vcs-* URLs to point at salsa.debian.org.
  * Bump debhelper compat to 11.
  * Bump standards version to 4.1.4.

 -- Timo Aaltonen   Thu, 22 Nov 2018 16:56:49 +0200

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1

---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.2 HWE stack update. (LP: #1798597)
  * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)

 -- Timo Aaltonen   Thu, 29 Nov 2018 00:09:03 +0200

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

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions

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

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1

---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport for 18.04.2 HWE stack update. (LP: #1798597)
  * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)

 -- Timo Aaltonen   Thu, 29 Nov 2018 00:09:03 +0200

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "ERROR Atomic update failure on pipe A"

2019-01-31 Thread Llord Llama

I understand that every user would like every bug they file to be
considered "Important".

In this case though we have around 23 people who have confirmed this bug
affects them on the three separate bug reports. It causes hanging and
forced hard shutdowns at unpredictable times as often as every 15
minutes or so. This means there is a high probability of user data loss
and even hardware damage.

I respectfully submit that it's reasonable to expect the importance of
this to be set to High.

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

Title:
  Frequent system freezing with i915 error "*ERROR* Atomic update
  failure on pipe A"

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-modesetting package in Ubuntu:
  New

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1812875] Re: ip6_gre: fix tunnel list corruption for x-netns

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

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

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

Title:
  ip6_gre: fix tunnel list corruption for x-netns

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: A kernel panic is seen when using some third-party software.

  Fix: Upstream commit ab5098fa25b9 ("ip6_gre: fix tunnel list
  corruption for x-netns").

  Test Case: Confirm that the panic no longer happens with the patch.

  Regression Potential: This is a simple fix and suitable for upstream
  stable, regressions are unlikely.

  ---

  The following upstream patch is missing in ubuntu-18.04: ab5098fa25b9
  ("ip6_gre: fix tunnel list corruption for x-netns").

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab5098fa25b9

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

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

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

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

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

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

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

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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

[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

Thanks. So the problem does seem to be with the Nvidia driver.

You might want to start by trying to uninstall "i386" packages like:

  sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386

and if that doesn't clear it up then:

  sudo apt --fix-broken install

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: wayland
  Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions

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

[Kernel-packages] [Bug 1721987] Re: No sound from right audio channel

2019-01-31 Thread Reda Borchardt

After reading the Linux audio sub system documentation I discovered
/sys/class/sound/hwC0D0 and hda-verb. That will hopefully do the trick.

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

Title:
  No sound from right audio channel

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

Bug description:
  No audio comes out of the right speaker on the laptop.  When playing a
  test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
  right-channel audio is never heard (i.e., it does not get converted
  into mono and played through the left speaker).

  When plugging in headphones, audio is heard from both channels.

  In Windows, both speakers work, so it is not a physical problem with
  the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 12:58:01 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HUAWEI HUAWEI MateBook X
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: HUAWEI MateBook X
  dmi.board.vendor: HUAWEI
  dmi.board.version: 2.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr:
  dmi.product.family: HUAWEI MateBook
  dmi.product.name: HUAWEI MateBook X
  dmi.product.version: 2.0
  dmi.sys.vendor: HUAWEI

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

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

[Kernel-packages] [Bug 1803246] Re: Ubuntu 18.10 is Unable to Suspend When Closing Lenovo E531 Laptop Lid

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

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

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

Title:
  Ubuntu 18.10 is Unable to Suspend When Closing Lenovo E531 Laptop Lid

Status in linux package in Ubuntu:
  Expired

Bug description:
  The trackpad of my Lenovo E531 Thinkpad Edge works when logged into
  18.10. When you close the lid the laptop normally goes into suspend
  (in 18.04), but fails to suspend in 18.10. The trackpad becomes
  unresponsive after the lid has been closed and the lid is opened
  again. See the response from dmesg below. Funny thing: This error does
  not occur when the power button is pressed and the trackpad is
  responsive (because a suspend was not attempted via the lid).

  I am using version: Ubuntu 4.18.0-10.11-generic 4.18.12


  According to dmesg:

  [ 650.163700] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [ 650.165107] Suspending console(s) (use no_console_suspend to debug)
  [ 650.165646] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 
TX register (-6).
  [ 650.165649] psmouse serio2: Failed to disable mouse on rmi4-00.fn03/serio0
  [ 650.165966] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 
TX register (-6).
  [ 650.166282] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 
TX register (-6).
  [ 650.166814] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
  [ 650.166816] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
  [ 650.166820] rmi4_physical rmi4-00: Failed to suspend functions: -6

  I have tried the following:
  - Update grub
  - Reinstalled xserver-xorg-input-synaptics
  - Disabled the trackpad via Gnome
  - Updated the BIOS to the latest available version

  This issue has only occured since I upgraded from 18.04 to 18.10.

  It would be great if 18.10 could suspend when the lid is closed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anthony5917 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-06-24 (142 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 68853EM
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=40873332-4c5a-4f82-b0a4-c88bb092b9c6 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  wayland-session cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-04 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HEET52WW (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 68853EM
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrHEET52WW(1.33):bd06/21/2018:svnLENOVO:pn68853EM:pvrThinkPadEdgeE531:rvnLENOVO:rn68853EM:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E531
  dmi.product.name: 68853EM
  dmi.product.sku: LENOVO_MT_6885_BU_Think_FM_ThinkPad Edge E531
  dmi.product.version: ThinkPad Edge E531
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814092] Re: ADT test failure: quota and zram smoke tests don't install modules-extra pkg

2019-01-31 Thread Po-Hsu Lin

A possible solution is to parse the kernel version, I will give it a
shot.

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  ADT test failure: quota and zram smoke tests don't install modules-
  extra pkg

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid

Bug description:
  This affects linux-gcp and linux-azure on ADT, because the method used
  to detect if the testcase is running in the cloud doesn't work on ADT.
  The method is used by the ubuntu_quota_smoke_test and
  ubuntu_zram_smoke_test testcases.

  --
  try:
  cloud  = os.environ['CLOUD']
  if cloud in ['azure', 'gcp']:
   pkgs.append('linux-modules-extra-' + cloud + '*')
  --

  Some ADT logs:
  cosmic/linux-gcp: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-gcp/20190116_172740_8090f@/log.gz

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

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

[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

2019-01-31 Thread Frederick Gibson

frederick@graphMetrix-1:~$ sudo apt install --reinstall libwayland-server0
[sudo] password for frederick: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libgl1-mesa-dri:i386 : Depends: libelf1:i386 (>= 0.142) but it is not going to 
be installed
 libnvidia-gl-390:i386 : Depends: libwayland-client0:i386 (>= 1.3.92) but it is 
not going to be installed
 Depends: libwayland-server0:i386 (>= 1.2.0) but it is 
not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: wayland
  Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau:

[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is

It looks like maybe the Nvidia driver has pulled in some i386
dependencies despite being amd64 itself.

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libwayland-server0 1.16.0-1ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc
  /libwayland-server0/changelog.Debian.gz', which is different from
  other instances of package libwayland-server0:i386

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  Incomplete

Bug description:
  Trying to install nvidia-driver-390 on Dell XPS 15 6570

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libwayland-server0 1.16.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jan 31 18:32:20 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-14-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed
  DuplicateSignature:
   package:libwayland-server0:1.16.0-1ubuntu1.1
   Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', 
which is different from other instances of package libelf1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: wayland
  Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different 
from other instances of package libwayland-server0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0HWTMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions

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

[Kernel-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

2019-01-31 Thread J B

Can confirm that removing xserver-xorg-input-synaptics fixes the issue.

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

Title:
  Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xinput package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  All the Fn keys are working (audio, mute, bright, volume and even
  wifi) except for enable/disable touchpad. Does not toggle the
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xinput 1.6.2-1build1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1)
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Mar 31 15:41:59 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.42, 4.15.0-12-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
     Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840]
  InstallationDate: Installed on 2018-03-09 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd
   Bus 001 Device 003: ID 248a:8366
   Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite S55t-C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash 
vt.handoff=1
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2015
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.20
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite S55t-C
  dmi.product.version: PSPUGU-00200D
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2019-01-31 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 1813683

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  linux-image-4.15.0-44-generic tty login not work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just updated my ubuntu 18.04 and received the linux-
  image-4.15.0-44-generic.

  After update and reboot the machine, my computer starts normally.

  Seems boot normally

  but when gets to the login screen (I'm not use any kind of graphical
  login manager, boot pure on console/text)

  I just need to press enter (doesn't matter if type my login or not),
  then starts a loop, like if my 'enter' key has some kind of mechanical
  defect.

  Keeps pressing 'enter' until I do a CTRL-C.

  If I press enter key again, starts all over again. Periodically
  pressing 'enter' key in lapse of seconds.

  To prevent, I just had to boot using linux-image-4.15.0-43-generic and
  could login normally.

  What can I provide to you look this? I think it's my first time here
  or one of firsts

  Thanks in advanced.

  Regards

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

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

[Kernel-packages] [Bug 1811566] Re: Backported commit breaks audio (fixed upstream)

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

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

Title:
  Backported commit breaks audio (fixed upstream)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  == Justification ==
  Commit 648e921888ad96ea3dc922739e96716ad3225d7f (clk: x86: Stop marking 
clocks as CLK_IS_CRITICAL) backported to Cosmic kernel fixed the bug that keeps 
unused clocks on, but it is breaking the audio support on some Chromebooks 
(Swanky / Clapper/ Gnawty) since we were not using
  the right clock in the cht_bsw_max98090_ti machine driver.

  == Fix ==
  a182ecd (ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards
   using pmc_plt_clk_0)
  984bfb3 (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)
  94ea56c (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk)

  These 3 patches can be cherry-picked to Cosmic.

  == Test ==
  Test kernel with these 3 patches could be found in:
  http://people.canonical.com/~phlin/kernel/lp-1811566-chromebook-Gnawty/

  Bug reporter stated that this kernel can fix the audio issue as
  expected.

  == Regression potential ==
  Low,
  changes are limited in the cht_bsw_max98090_ti driver with a new DMI based 
quirk table that contains these 3 Chromebook models and some logic to determine 
the right clock to use.


  It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was
  backported to ubuntu's 4.18 kernel. That commit breaks audio for some
  devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are
  fixed, with patch  on commit:

  47148001ae12292984ba1b38d9babefb9a46cd3e
  ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook 
Gnawty

  Bug reported:

  https://bugzilla.kernel.org/show_bug.cgi?id=201787

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

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

[Kernel-packages] [Bug 1798776] Re: kvm_stat : missing python dependency

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

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

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

Title:
  kvm_stat : missing python dependency

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  After installing linux-tools-host, the included kvm_stat utility won't
  work:

  root@ubuntu:~# kvm_stat 
  -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or 
directory

  Reason is that there is apparently no dependency on a python package
  from the linux-tools-host package.

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

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

[Kernel-packages] [Bug 1812728] Re: linux-gcp: Reduce boot latency due to RAID6_PQ

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

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

Title:
  linux-gcp: Reduce boot latency due to RAID6_PQ

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Bionic:
  Fix Committed

Bug description:
  For an n1-standard-2 with ubuntu-1604, we spend around 600
  milliseconds during boot on computing the best raid6 recovery
  algorithm seen in the following lines of the kernel logs:

  ... 
  [ 2.216022] raid6: sse2x1 gen() 8570 MB/s 
  [ 2.264029] raid6: sse2x1 xor() 6467 MB/s 
  [ 2.312030] raid6: sse2x2 gen() 10602 MB/s 
  [ 2.360021] raid6: sse2x2 xor() 6999 MB/s 
  [ 2.412028] raid6: sse2x4 gen() 12483 MB/s 
  [ 2.464022] raid6: sse2x4 xor() 8607 MB/s 
  [ 2.516024] raid6: avx2x1 gen() 16712 MB/s 
  [ 2.568020] raid6: avx2x1 xor() 12050 MB/s 
  [ 2.620019] raid6: avx2x2 gen() 19393 MB/s 
  [ 2.672024] raid6: avx2x2 xor() 12406 MB/s 
  [ 2.724034] raid6: avx2x4 gen() 22330 MB/s 
  [ 2.776029] raid6: avx2x4 xor() 15196 MB/s 
  [ 2.780440] raid6: using algorithm avx2x4 gen() 22330 MB/s 
  [ 2.786035] raid6:  xor() 15196 MB/s, rmw enabled 
  [ 2.791196] raid6: using avx2x2 recovery algorithm 
  ... 

  It would be desirable to reduce or eliminate this delay.

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

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

[Kernel-packages] [Bug 1813683] Re: linux-image-4.15.0-44-generic tty login not work

2019-01-31 Thread Po-Hsu Lin

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

** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

** Tags added: bionic

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

Title:
  linux-image-4.15.0-44-generic tty login not work

Status in linux package in Ubuntu:
  New

Bug description:
  I just updated my ubuntu 18.04 and received the linux-
  image-4.15.0-44-generic.

  After update and reboot the machine, my computer starts normally.

  Seems boot normally

  but when gets to the login screen (I'm not use any kind of graphical
  login manager, boot pure on console/text)

  I just need to press enter (doesn't matter if type my login or not),
  then starts a loop, like if my 'enter' key has some kind of mechanical
  defect.

  Keeps pressing 'enter' until I do a CTRL-C.

  If I press enter key again, starts all over again. Periodically
  pressing 'enter' key in lapse of seconds.

  To prevent, I just had to boot using linux-image-4.15.0-43-generic and
  could login normally.

  What can I provide to you look this? I think it's my first time here
  or one of firsts

  Thanks in advanced.

  Regards

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

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

[Kernel-packages] [Bug 1813683] [NEW] linux-image-4.15.0-44-generic tty login not work

You have been subscribed to a public bug:

I just updated my ubuntu 18.04 and received the linux-
image-4.15.0-44-generic.

After update and reboot the machine, my computer starts normally.

Seems boot normally

but when gets to the login screen (I'm not use any kind of graphical
login manager, boot pure on console/text)

I just need to press enter (doesn't matter if type my login or not),
then starts a loop, like if my 'enter' key has some kind of mechanical
defect.

Keeps pressing 'enter' until I do a CTRL-C.

If I press enter key again, starts all over again. Periodically pressing
'enter' key in lapse of seconds.

To prevent, I just had to boot using linux-image-4.15.0-43-generic and
could login normally.

What can I provide to you look this? I think it's my first time here or
one of firsts

Thanks in advanced.

Regards

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

-- 
linux-image-4.15.0-44-generic tty login not work
https://bugs.launchpad.net/bugs/1813683
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 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2019-01-31 Thread jasonubuntu

I am using Lenovo Yoga 260 with OneLink+ Dock and just started to have the same 
problem with Ubuntu freezing.  I am using 18.04.1.  Symptoms:
(1) If I have it connected when I power up, it will hang and you can only hold 
down the power down button.
(2) If I connect the Dock link after I power up BUT before I login, it will 
also hang
(3) After I login, connect the Dock link, works fine.  But noticed if it goes 
to screen lock, it will hang again but have not tested if this happens every 
time.

$ uname -a
Linux jtsang-ThinkPad-Yoga-260 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 
16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1812797] Re: [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr

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

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

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

Title:
  [SRU] Fix Xorg crash with nomodeset when BIOS enable 64-bit fb addr

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On dual GPU platform, BIOS set frame buffer addr to 64-bit, usually when 
CSM=NO setting in BIOS.
  When no proper GPU driver loaded, Xorg driver will use the wrong fb addr, 
then crash.

  [Fix]
  Add 64-bit efifb support, make Xorg find the correct GPU fb addr.
  If still failed, use the first GPU as default.

  [Test]
  Tested on Intel and NV dual GPU platform. Works fine.

  [Regression Potential]
  Upstream fix, low risk.
  Verified on ThinkPad P1/P52.

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

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

[Kernel-packages] [Bug 1812812] Re: Fix non-working QCA Rome Bluetooth after S3

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

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

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

Title:
  Fix non-working QCA Rome Bluetooth after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Sometimes QCA Rome Bluetooth USB host doesn't work after S3:
  [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
  [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)

  This is due to USB core enables LPM two times after S3.

  [Fix]
  Only enable LPM once.

  [Test]
  The Bluetooth USB works all the time after applying the fix.

  [Regression Potential]
  Low. Enabling a hardware feature twice in a row isn't right, I'd be surprise 
if any hardware relies on this driver behavior.

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

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

[Kernel-packages] [Bug 1813921] Re: The ubuntu doesn't work when there is a second monitor and the user locks the screen.

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1813663, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  The ubuntu doesn't work when there is a second monitor and the user
  locks the screen.

Status in linux package in Ubuntu:
  New

Bug description:
  Initial Setup to reproduce the first issue:
  1. Have the last Ubuntu (18.04) updated.
  2. Have a second monitor.

  First bug Description:
  1. Try to starts the Ubuntu.

  Actual Results:
  1. The Ubuntu can't start.

  Initial Setup to reproduce the second issue:
  1. Have the last Ubuntu (18.04) updated.
  2. Have a second monitor ready (not connected) to connect.

  Second bug description:
  1. With the Ubuntu started, connect the second monitor and then lock the 
screen.
  2. Try to unlock Ubuntu.

  Actual Results:
  2. The mouse and keyboard don't work and the screen can't be unlocked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 07:16:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  MachineType: LENOVO 20B7008BBR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=e1c74834-7cc4-44fb-94a2-06206608a746 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET79WW (2.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7008BBR
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B7008BBR:pvrThinkPadT440:rvnLENOVO:rn20B7008BBR:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440
  dmi.product.name: 20B7008BBR
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jan 29 14:59:13 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

[Kernel-packages] [Bug 1813921] [NEW] The ubuntu doesn't work when there is a second monitor and the user locks the screen.

You have been subscribed to a public bug:

Initial Setup to reproduce the first issue:
1. Have the last Ubuntu (18.04) updated.
2. Have a second monitor.

First bug Description:
1. Try to starts the Ubuntu.

Actual Results:
1. The Ubuntu can't start.

Initial Setup to reproduce the second issue:
1. Have the last Ubuntu (18.04) updated.
2. Have a second monitor ready (not connected) to connect.

Second bug description:
1. With the Ubuntu started, connect the second monitor and then lock the screen.
2. Try to unlock Ubuntu.

Actual Results:
2. The mouse and keyboard don't work and the screen can't be unlocked.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 30 07:16:30 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
MachineType: LENOVO 20B7008BBR
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=e1c74834-7cc4-44fb-94a2-06206608a746 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET79WW (2.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B7008BBR
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20B7008BBR:pvrThinkPadT440:rvnLENOVO:rn20B7008BBR:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T440
dmi.product.name: 20B7008BBR
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Jan 29 14:59:13 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
The ubuntu doesn't work when there is a second monitor and the user locks the 
screen.
https://bugs.launchpad.net/bugs/1813921
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 1814162] Re: Xorg freeze

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1813663, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine on the latest ubuntu version 4.15.0-44-generic,
  it turns my display completely black and unresponsive. This is only
  when I have my dock (with external displays in). After it freezes
  however, removing the dock has no effect. Booting back into
  4.15.0-43-generic has fixed the problem so this is a regression bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 14:25:01 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081c]
  InstallationDate: Installed on 2018-10-17 (106 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.2
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2019-01-31 Thread Ubuntu Kernel Bot

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

This change was made by a bot.

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

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine on the latest ubuntu version 4.15.0-44-generic,
  it turns my display completely black and unresponsive. This is only
  when I have my dock (with external displays in). After it freezes
  however, removing the dock has no effect. Booting back into
  4.15.0-43-generic has fixed the problem so this is a regression bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 14:25:01 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081c]
  InstallationDate: Installed on 2018-10-17 (106 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.2
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1814162] Re: Xorg freeze

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

** Package changed: xorg (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/1814162

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine on the latest ubuntu version 4.15.0-44-generic,
  it turns my display completely black and unresponsive. This is only
  when I have my dock (with external displays in). After it freezes
  however, removing the dock has no effect. Booting back into
  4.15.0-43-generic has fixed the problem so this is a regression bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 14:25:01 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081c]
  InstallationDate: Installed on 2018-10-17 (106 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude 7490
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.2
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1813127] Re: ptrace-tm-spd-gpr in powerpc/ptrace from ubuntu_kerenl_selftests failed on Bionic P8

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

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

Title:
  ptrace-tm-spd-gpr in powerpc/ptrace from ubuntu_kerenl_selftests
  failed on Bionic P8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Justification ==
  ptrace-tm-spd-gpr in powerpc/ptrace will fail with Power8 on Bionic:
  $ sudo ./ptrace-tm-spd-gpr 
  test: ptrace_tm_spd_gpr
  tags: git_version:c186097-dirty
  !! killing ptrace_tm_spd_gpr
  !! child died by signal 15
  failure: ptrace_tm_spd_gpr

  This is due to a segmentation fault that happens on the child process
  prior to setting cptr[2] = 1. This causes the parent process to wait
  forever at 'while (!pptr[2])' and the test to be killed by the test
  harness framework by timeout.

  == Fix ==
  48dc0ef (selftests/powerpc: Fix ptrace tm failure)
  This patch can be cherry-picked for Bionic.

  == Test == 
  After the patch, the test will pass with:
  $ sudo ./ptrace-tm-spd-gpr
  test: ptrace_tm_spd_gpr
  tags: git_version:c186097-dirty
  success: ptrace_tm_spd_gpr

  == Regression potential ==
  None, change for the testing tool only.


  This issue only exist in Bionic P8:
  $ sudo ./ptrace-tm-spd-gpr
  test: ptrace_tm_spd_gpr
  tags: git_version:c186097-dirty
  !! killing ptrace_tm_spd_gpr
  !! child died by signal 15
  failure: ptrace_tm_spd_gpr

  Result on P9:
  $ sudo ./ptrace-tm-spd-gpr
  test: ptrace_tm_spd_gpr
  tags: git_version:unknown
  [SKIP] Test skipped on line 125
  skip: ptrace_tm_spd_gpr

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 06:57 seq
   crw-rw 1 root audio 116, 33 Jan 24 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [ 3531.661373] ptrace-tm-spd-g[22437]: unhandled signal 11 at 
 nip 0f7428473330 lr 0f742847317c code 1
  Date: Thu Jan 24 07:59:27 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0
  ProcLoadAvg: 0.32 0.53 0.33 1/1478 23438
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 
2018
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.694 GHz (cpu 159)
   max: 3.694 GHz (cpu 4)
   avg: 3.694 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

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

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

[Kernel-packages] [Bug 1814162] [NEW] Xorg freeze

You have been subscribed to a public bug:

When I lock my machine on the latest ubuntu version 4.15.0-44-generic,
it turns my display completely black and unresponsive. This is only when
I have my dock (with external displays in). After it freezes however,
removing the dock has no effect. Booting back into 4.15.0-43-generic has
fixed the problem so this is a regression bug.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 31 14:25:01 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:081c]
InstallationDate: Installed on 2018-10-17 (106 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Latitude 7490
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.2
dmi.board.name: 0KP0FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7490
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1814162
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 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

2019-01-31 Thread Bug Watch Updater

** Changed in: ndctl
   Status: New => Fix Released

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

Title:
  NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840

Status in ndctl:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in ndctl package in Ubuntu:
  New

Bug description:
  On ubuntu 18.04.1 :

  1°) With 4.15.0-43 two default namespaces in raw mode are visible
  while there shouldn't be any but no settings change could be applied.

  root@server:~# ndctl list -R
  [
{
  "dev":"region1",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":1,
  "persistence_domain":"unknown"
},
{
  "dev":"region0",
  "size":103079215104,
  "available_size":0,
  "type":"pmem",
  "numa_node":0,
  "persistence_domain":"unknown"
}
  ]

  root@server:~# ndctl list
  [
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem1",
  "numa_node":1
},
{
  "dev":"namespace0.0",
  "mode":"raw",
  "size":103079215104,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}
  ]

  root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem 
--mode=sector -f
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host 
(256 byte) labels
  libndctl: sizeof_namespace_index: nmem6:

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

linux (4.15.0-45.48) bionic; urgency=medium

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)

  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"

  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

 -- Stefan Bader   Tue, 29 Jan 2019 16:39:15
+0100


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

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

Title:
  External monitors does not work anymore 4.15.0-44

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

Bug description:
  I am using a docking station for my laptop. After install the
  4.15.0-44 update my external monitors goes undetected after logging in
  or having the laptop closed.

  I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2)
  Graphics.

  Going back to the 4.15.0-43 version makes it all work fine again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  2407 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4
  InstallationDate: Installed on 2018-10-17 (103 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20HF004MMX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF004MMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF004MMX
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813133] Re: rpi-cm3 dtb is not present in the arm64 variant

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-raspi2 (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  rpi-cm3 dtb is not present in the arm64 variant

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Cosmic:
  Fix Committed

Bug description:
  Impact:

  The dtb for the Raspberry CM3 board is not shipped in the Bionic
  -raspi2 kernel arm64 variant.

  Fix:

  The dtb for the cm3 board was not compiled at all, in the arm64 arch -
  apply the attached patch and recompile.

  How to test:

  The linux-modules-*-raspi2_arm64.deb should contain the bcm2710-rpi-
  cm3 dtb now:

  $ dpkg -x linux-modules-4.15.0-1031-raspi2_4.15.0-1031.33_arm64.deb foobar
  ...
  $ ls -l foobar/lib/firmware/4.15.0-1031-raspi2/device-tree/broadcom/
  total 92
  -rw-r--r-- 1 ppisati ppisati 24566 Jan 23 12:59 bcm2710-rpi-3-b-plus.dtb
  -rw-r--r-- 1 ppisati ppisati 24303 Jan 23 12:59 bcm2710-rpi-3-b.dtb
  -rw-r--r-- 1 ppisati ppisati 23015 Jan 23 12:59 bcm2710-rpi-cm3.dtb
  -rw-r--r-- 1 ppisati ppisati 17451 Jan 23 12:59 bcm2837-rpi-3-b.dtb

  Regression potential:

  The patch is trivial - it just builds the cm3 dtb if arch==arm64, and
  doesn't modify any code, so the regression potential is zero.

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-01-31 Thread Paul Dufresne

Someone said:
"I tried this with a Ubuntu 17.10 and could not boot. I had to use a rescue 
boot and remove the lines again to get it up and running."
from:https://askubuntu.com/questions/794865/16-04-ati-mobility-radeon-x1600-full-resolution-flickering
So, try with care!

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

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

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

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True

[Kernel-packages] [Bug 1785816] Re: Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING

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

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

Title:
  Consider enabling CONFIG_NETWORK_PHY_TIMESTAMPING

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

Bug description:
  SRU Justification

  Impact: CONFIG_NETWORK_PHY_TIMESTAMPING is disabled, preventing PTP
  time synchronization using the DP83640 PHYTER.

  Fix: Enable this option and set CONFIG_DP83640_PHY=m to enable the
  DP83640 PHYTER driver.

  Regression Potential: The kconfig help text warns of adding overhead
  to network tx and rx, but our analysis finds this to be negligible
  (see comment #6). Beyond this we are enabling a new driver which does
  little unless timestamping is explicitly activated, so regressions are
  not expected.

  ---

  Hi folks, is there a reason we do not enable
  CONFIG_NETWORK_PHY_TIMESTAMPING ? I'm not sure of the tradeoffs but I
  think this config option is required for PTP time syncronization which
  would be useful in telco and financial (and OCD :)) environments.

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-01-31 Thread Paul Dufresne

I guess I would rather add the two option lines (with same indentation) to:
file:///usr/share/X11/xorg.conf.d/10-radeon.conf

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-01-31 Thread Paul Dufresne

The bug have been reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=108514

https://forums.linuxmint.com/viewtopic.php?t=229387
suggest the bug could be "fixed" by creating 
/usr/share/X11/xorg.conf.d/20-radeon.conf with:

Section "Device"
Identifier "Radeon"
Driver "radeon"
Option "AccelMethod" "glamor"
Option "TearFree" "on"
EndSection

Someone could try?

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

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1804040] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [ERROR: Kernel configuration is invalid.]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build [ERROR: Kernel configuration is invalid.]

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  failed to update my system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-39-generic
  Date: Mon Nov 19 23:00:47 2018
  InstallationDate: Installed on 2018-09-16 (64 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 390.77-0ubuntu0.18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1804040/+subscriptions

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-01-31 Thread Treviño

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: Fix Committed => In Progress

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  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:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-01-31 Thread Treviño

Augustin,

What version of ubuntu have you tested?
Can you please paste here the output of the command
  apt-cache policy linux-image-generic upower gnome-control-center gnome-shell


Are you also using a fixed kernel?

** Changed in: upower (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Triaged
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  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:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1748983] Missing SRU information

2019-01-31 Thread Brian Murray

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

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

Title:
  Generate per-machine MOK for dkms signing

Status in dkms package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released

Bug description:
  shim-signed's update-secureboot-policy should allow creating a
  machine-owner key, and using this for signing kernel modules built via
  DKMS. Key generation and enrolling should be made as easy as possible
  for users.

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

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

[Kernel-packages] [Bug 1814015] Re: After upgrade to kernel .44 docking station and external monitors not working

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  After upgrade to kernel .44 docking station and external monitors not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading the kernel has resulted in displays crashing and external
  displays not working.

  Release: Ubuntu 18.0.4 LTS

  dist-upgrade

  Normal boot is expected - after entering encryption password for hard
  disk get black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 20:45:30 2019
  InstallationDate: Installed on 2016-11-10 (811 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (258 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1814084] Re: The screen went black - had to restart. Have happened several times today..

It is possible this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663. Please
confirm by reviewing that bug to see if your conditions are similar. At
your earliest convenience could you please try the 4.15.0-45 to it it
resolves your 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/1814084

Title:
  The screen went black - had to restart. Have happened several times
  today..

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The screen went black - had to restart. Have happened several times
  today..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  llk1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 12:35:03 2019
  HibernationDevice: RESUME=UUID=42fc63eb-406d-4733-b480-1ad65586
  InstallationDate: Installed on 2018-10-25 (98 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP EliteBook 850 G5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=beba2df7-1067-4875-bc5e-ae2e91661d24 ro quiet splash acpi_osi= 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q78 Ver. 01.03.00
  dmi.board.name: 83B2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 04.53.00
  dmi.chassis.asset.tag: 5CG8398P9Y
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ78Ver.01.03.00:bd07/18/2018:svnHP:pnHPEliteBook850G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 850 G5
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-01-31 Thread Christopher M. Penalver

Selwyn, the issue you are reporting is an upstream one. Could you please
report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: linux-usb CC: Mathias Nyman and Greg Kroah-Hartman)?

This article was written for folks who don't know anything about linux,
so it's easy to follow.

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.

** Description changed:

  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/
  
  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.
+ 
+ WORKAROUND: Disable XHC1 prior to sleeping via:
+ # echo XHC1 > /proc/acpi/wakeup
  
  Sidenote: thanks to penalvch for explaining how to report this!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  WORKAROUND: Disable XHC1 prior to sleeping via:
  # echo XHC1 > /proc/acpi/wakeup

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2019-01-31 Thread Joseph Salisbury

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1814117] Re: System hangs when a Dell WD15 dock station is plugged

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

** This bug has been marked a duplicate of bug 1813663
   External monitors does not work anymore 4.15.0-44

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

Title:
  System hangs when a Dell WD15 dock station is plugged

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With the kernel packets in version 4.15.0-43 (the ones I'm running to report 
this bug), I can plug my Dell WD15 dock station normally on the USB-C connector 
of my laptop, before or after booting it: everything works fine.
  When I upgrade to the latest kernel (i.e. install linux-XXX-4.15.0.44 with 
XXX=image, headers, modules and modules-extra), my laptop cannot boot ubuntu 
with the WD15 dock plugged in. It boots normally without WD15, can use normally 
a USB-C memory stick plugged in the same connector, but hangs whenever the WD15 
dock is plugged in: black screen, no reaction to the laptop keyboard even when 
caps lock is pressed (the corresponding LED does not turn on), must reboot with 
a long action on the  power-off button.
  The problem is really specific to 4.15.0.44 and is not present in 4.15.0.43. 
Whit the new version installed, choosing the old kernel in the GRUB menu gives 
a working system. I now un-installed the new version and it works well.

  Enclosed file: Portion of /var/log/kern.log showing a boot sequence
  with WD15 plugged. It begins to differ from the sequence with WD15
  unplugged at line 685 (looking for usb devices), contains a warning at
  line 850 and a OOPS at line 951

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1248 F pulseaudio
delannoy   1712 F pulseaudio
  Date: Thu Jan 31 15:42:55 2019
  InstallationDate: Installed on 2017-09-20 (497 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude 5480
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=4266b673-814e-442f-b0fb-f65e55c0c0ab ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (261 days ago)
  dmi.bios.date: 11/12/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0T96NR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0T96NR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5480
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1814151] Re: Screen freezes

I believe this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663. Please
confirm by reviewing that bug to see if your conditions are similar.  At
your earliest convenience could you please try the 4.15.0-45 to it it
resolves your 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/1814151

Title:
  Screen freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes after wake up from suspend mode on Acer Aspire V3-571G.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 20:57:28 2019
  HibernationDevice: RESUME=UUID=a27531fc-cfed-43e8-a74e-35d79f38791c
  InstallationDate: Installed on 2018-08-26 (158 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=ef195b2c-8777-41a7-ba3d-9fcf3765739d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd12/04/2012:svnAcer:pnAspireV3-571G:pvrV2.09:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.09:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 400397] Re: Errors (hanging, only continue with Ctrl-c) while prosessing kexec-tools

2019-01-31 Thread Bug Watch Updater

** Changed in: kexec-tools (Debian)
   Status: Unknown => Fix Released

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

Title:
  Errors (hanging,only continue with Ctrl-c) while prosessing kexec-
  tools

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  Karmic
  Binary package hint: kexec-tools

  jarkko@gandalf:/boot/grub$ sudo dpkg --configure -a -D2000
  Setting up kexec-tools (2009-2.0.0ubuntu10) ...
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin

   (hangs here forever) x

  ^Cdpkg: error processing kexec-tools (--configure):
   subprocess installed post-installation script killed by signal (Interrupt)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.31-3-generic
  Errors were encountered while processing:
   kexec-tools
  jarkko@gandalf:/boot/grub$

  Same thing with apt-get dist-upgrade.

  update-grub works when run alone;
  jarkko@gandalf:/boot/grub$ sudo update-grub 
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  jarkko@gandalf:/boot/grub$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/400397/+subscriptions

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

[Kernel-packages] [Bug 1814170] Re: Disco update: v4.19.19 upstream stable release

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     v4.19.19 upstream stable release
     from git://git.kernel.org/
  
  amd-xgbe: Fix mdio access for non-zero ports and clause 45 PHYs
  net: bridge: Fix ethernet header pointer before check skb forwardable
  net: Fix usage of pskb_trim_rcsum
  net: phy: marvell: Errata for mv88e6390 internal PHYs
  net: phy: mdio_bus: add missing device_del() in mdiobus_register() error 
handling
  net/sched: act_tunnel_key: fix memory leak in case of action replace
  net_sched: refetch skb protocol for each filter
  openvswitch: Avoid OOB read when parsing flow nlattrs
  vhost: log dirty page correctly
  mlxsw: pci: Increase PCI SW reset timeout
  net: ipv4: Fix memory leak in network namespace dismantle
  mlxsw: spectrum_fid: Update dummy FID index
  mlxsw: pci: Ring CQ's doorbell before RDQ's
  net/sched: cls_flower: allocate mask dynamically in fl_change()
  udp: with udp_segment release on error path
- ip6_gre: fix tunnel list corruption for x-netns
  erspan: build the header with the right proto according to erspan_ver
  net: phy: marvell: Fix deadlock from wrong locking
  ip6_gre: update version related info when changing link
  tcp: allow MSG_ZEROCOPY transmission also in CLOSE_WAIT state
  mei: me: mark LBG devices as having dma support
  mei: me: add denverton innovation engine device IDs
  USB: leds: fix regression in usbport led trigger
  USB: serial: simple: add Motorola Tetra TPG2200 device id
  USB: serial: pl2303: add new PID to support PL2303TB
  ceph: clear inode pointer when snap realm gets dropped by its inode
  ASoC: atom: fix a missing check of snd_pcm_lib_malloc_pages
  ASoC: rt5514-spi: Fix potential NULL pointer dereference
  ASoC: tlv320aic32x4: Kernel OOPS while entering DAPM standby mode
  clk: socfpga: stratix10: fix rate calculation for pll clocks
  clk: socfpga: stratix10: fix naming convention for the fixed-clocks
  inotify: Fix fd refcount leak in inotify_add_watch().
  ALSA: hda/realtek - Fix typo for ALC225 model
  ALSA: hda - Add mute LED support for HP ProBook 470 G5
  ARCv2: lib: memeset: fix doing prefetchw outside of buffer
  ARC: adjust memblock_reserve of kernel memory
  ARC: perf: map generic branches to correct hardware condition
  s390/mm: always force a load of the primary ASCE on context switch
  s390/early: improve machine detection
  s390/smp: fix CPU hotplug deadlock with CPU rescan
  misc: ibmvsm: Fix potential NULL pointer dereference
  char/mwave: fix potential Spectre v1 vulnerability
  mmc: dw_mmc-bluefield: : Fix the license information
  mmc: meson-gx: Free irq in release() callback
  staging: rtl8188eu: Add device code for D-Link DWA-121 rev B1
  tty: Handle problem if line discipline does not have receive_buf
  uart: Fix crash in uart_write and uart_put_char
  tty/n_hdlc: fix __might_sleep warning
  hv_balloon: avoid touching uninitialized struct page during tail onlining
  Drivers: hv: vmbus: Check for ring when getting debug info
  vgacon: unconfuse vc_origin when using soft scrollback
  CIFS: Fix possible hang during async MTU reads and writes
  CIFS: Fix credits calculations for reads with errors
  CIFS: Fix credit calculation for encrypted reads with errors
  CIFS: Do not reconnect TCP session in add_credits()
  smb3: add credits we receive from oplock/break PDUs
  Input: xpad - add support for SteelSeries Stratus Duo
  Input: input_event - provide override for sparc64
  Input: uinput - fix undefined behavior in uinput_validate_absinfo()
  acpi/nfit: Block function zero DSMs
  acpi/nfit: Fix command-supported detection
  scsi: ufs: Use explicit access size in ufshcd_dump_regs
  dm thin: fix passdown_double_checking_shared_status()
  dm crypt: fix parsing of extended IV arguments
  drm/amdgpu: Add APTX quirk for Lenovo laptop
  KVM: x86: Fix single-step debugging
  KVM: x86: Fix PV IPIs for 32-bit KVM host
  KVM: x86: WARN_ONCE if sending a PV IPI returns a fatal error
  kvm: x86/vmx: Use kzalloc for cached_vmcs12
  KVM/nVMX: Do not validate that posted_intr_desc_addr is page aligned
  x86/pkeys: Properly copy pkey state at fork()
  x86/selftests/pkeys: Fork() to check for state being preserved
  x86/kaslr: Fix incorrect i8254 outb() parameters
  x86/entry/64/compat: Fix stack switching for XEN PV
- posix-cpu-timers: Unbreak timer rearming
  net: sun: cassini: Cleanup license conflict
  irqchip/gic-v3-its: Align PCI Multi-MSI allocation on their size
  can: dev: __can_get_echo_skb(): fix bogous check for non-existing skb by 
removing it
  can: bcm: check timer

[Kernel-packages] [Bug 1814170] [NEW] Disco update: v4.19.19 upstream stable release

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v4.19.19 upstream stable release
   from git://git.kernel.org/

amd-xgbe: Fix mdio access for non-zero ports and clause 45 PHYs
net: bridge: Fix ethernet header pointer before check skb forwardable
net: Fix usage of pskb_trim_rcsum
net: phy: marvell: Errata for mv88e6390 internal PHYs
net: phy: mdio_bus: add missing device_del() in mdiobus_register() error 
handling
net/sched: act_tunnel_key: fix memory leak in case of action replace
net_sched: refetch skb protocol for each filter
openvswitch: Avoid OOB read when parsing flow nlattrs
vhost: log dirty page correctly
mlxsw: pci: Increase PCI SW reset timeout
net: ipv4: Fix memory leak in network namespace dismantle
mlxsw: spectrum_fid: Update dummy FID index
mlxsw: pci: Ring CQ's doorbell before RDQ's
net/sched: cls_flower: allocate mask dynamically in fl_change()
udp: with udp_segment release on error path
erspan: build the header with the right proto according to erspan_ver
net: phy: marvell: Fix deadlock from wrong locking
ip6_gre: update version related info when changing link
tcp: allow MSG_ZEROCOPY transmission also in CLOSE_WAIT state
mei: me: mark LBG devices as having dma support
mei: me: add denverton innovation engine device IDs
USB: leds: fix regression in usbport led trigger
USB: serial: simple: add Motorola Tetra TPG2200 device id
USB: serial: pl2303: add new PID to support PL2303TB
ceph: clear inode pointer when snap realm gets dropped by its inode
ASoC: atom: fix a missing check of snd_pcm_lib_malloc_pages
ASoC: rt5514-spi: Fix potential NULL pointer dereference
ASoC: tlv320aic32x4: Kernel OOPS while entering DAPM standby mode
clk: socfpga: stratix10: fix rate calculation for pll clocks
clk: socfpga: stratix10: fix naming convention for the fixed-clocks
inotify: Fix fd refcount leak in inotify_add_watch().
ALSA: hda/realtek - Fix typo for ALC225 model
ALSA: hda - Add mute LED support for HP ProBook 470 G5
ARCv2: lib: memeset: fix doing prefetchw outside of buffer
ARC: adjust memblock_reserve of kernel memory
ARC: perf: map generic branches to correct hardware condition
s390/mm: always force a load of the primary ASCE on context switch
s390/early: improve machine detection
s390/smp: fix CPU hotplug deadlock with CPU rescan
misc: ibmvsm: Fix potential NULL pointer dereference
char/mwave: fix potential Spectre v1 vulnerability
mmc: dw_mmc-bluefield: : Fix the license information
mmc: meson-gx: Free irq in release() callback
staging: rtl8188eu: Add device code for D-Link DWA-121 rev B1
tty: Handle problem if line discipline does not have receive_buf
uart: Fix crash in uart_write and uart_put_char
tty/n_hdlc: fix __might_sleep warning
hv_balloon: avoid touching uninitialized struct page during tail onlining
Drivers: hv: vmbus: Check for ring when getting debug info
vgacon: unconfuse vc_origin when using soft scrollback
CIFS: Fix possible hang during async MTU reads and writes
CIFS: Fix credits calculations for reads with errors
CIFS: Fix credit calculation for encrypted reads with errors
CIFS: Do not reconnect TCP session in add_credits()
smb3: add credits we receive from oplock/break PDUs
Input: xpad - add support for SteelSeries Stratus Duo
Input: input_event - provide override for sparc64
Input: uinput - fix undefined behavior in uinput_validate_absinfo()
acpi/nfit: Block function zero DSMs
acpi/nfit: Fix command-supported detection
scsi: ufs: Use explicit access size in ufshcd_dump_regs
dm thin: fix passdown_double_checking_shared_status()
dm crypt: fix parsing of extended IV arguments
drm/amdgpu: Add APTX quirk for Lenovo laptop
KVM: x86: Fix single-step debugging
KVM: x86: Fix PV IPIs for 32-bit KVM host
KVM: x86: WARN_ONCE if sending a PV IPI returns a fatal error
kvm: x86/vmx: Use kzalloc for cached_vmcs12
KVM/nVMX: Do not validate that posted_intr_desc_addr is page aligned
x86/pkeys: Properly copy pkey state at fork()
x86/selftests/pkeys: Fork() to check for state being preserved
x86/kaslr: Fix incorrect i8254 outb() parameters
x86/entry/64/compat: Fix stack switching for XEN PV
net: sun: cassini: Cleanup license conflict
irqchip/gic-v3-its: Align PCI Multi-MSI allocation on their size
can: dev: __can_get_echo_skb(): fix bogous check for non-existing skb by 
removing it
can: bcm: check timer values before ktime conversion
can: flexcan: fix NULL pointer exception during bringup
vt: make vt_console_print() compatible with the unicode screen buffer
vt: always call notifier with the console lock held
vt: invoke notifier on screen size change
drm/meson: Fix atomic mode

[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2019-01-31 Thread Markus Malkusch

>  when I wanted to start a new session while docked.

I mean a new X session.

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2019-01-31 Thread Markus Malkusch

I think I'm also affected by this issue (Thinkpad T450s). When changing
the power management behavior for a closed lid (AC and Battery) to not
suspend, I have no issues. I can then dock and undock. So this would be
a work around.

This issue is clearly related to the suspending behavior of a closed lid
during docking. I even get a freeze when I would simply shutdown the
system. I think it even freezes when I wanted to start a new session
while docked.


$ uname -a
Linux markushost 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-01-31 Thread Agustin Barto

I've tested the proposed updates and it seems to work with one minor
caveat: If I unplug and plug the AC adapter, it takes a little while for
the system to notice the change if it's near full charge (around 2
minutes). I think it's only a minor inconvenience.

I've also tested that it properly detects the correct status coming of a
cold boot or a resume and it worked just fine. I'd say this one's 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in upower source package in Bionic:
  In Progress
Status in gnome-control-center source package in Cosmic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  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:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 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: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1813672] Re: 4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked

2019-01-31 Thread Brandon Rochon

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

Confirmed 4.15.0-45 fixes the problem. 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/1813672

Title:
  4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, lock the screen while the laptop is docked.  Box will go
  into some hung state where the only solution is to hard poweroff.
  Doesn't happen while undocked.  Reverting to 4.15.0-43 kernel fixes
  the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1218 F pulseaudio
rochon 2115 F pulseaudio
  Date: Mon Jan 28 14:15:24 2019
  InstallationDate: Installed on 2017-05-25 (613 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HGS0CB00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=d26c36c8-1296-4878-a755-84517190e94c ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (265 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS0CB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HGS0CB00:pvrThinkPadT470s:rvnLENOVO:rn20HGS0CB00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HGS0CB00
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813795] Re: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel

2019-01-31 Thread rathboma

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

Same as limod using a Thinkpad X1 Carbon 5th gen. Totally freezes the
system actually, doesn't just blackout the monitors. Nothing responds.

Also happens with 4.15.0-45

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

Title:
Dell tablet crashes when plugged into docking station with 4.15.0-44
kernel

Status in linux package in Ubuntu:
Confirmed

Bug description:
I have a Dell 5290 2-in-1 tablet that has been running Ubuntu 18.04
successfully for several months. Today I upgraded the kernel from
4.15.0-43 to 4.15.0-44. The tablet functions normally until it is
plugged into its docking station, then the screen freezes.

Technically, the screen flickers a few times, then goes blank, leaving
only the frozen mouse pointer. The system is still running, though as
I can ssh into my tablet. sudo reboot will not reboot the tablet, but
sudo reboot -f will.

When I force the tablet to load 4.15.0-43, the tablet functions
normally. i.e. even when I plug it into its docking station, it
continues to perform properly. It's only with 4.15.0-44 that it
freezes.

As you can see from the linked question and forum thread, this appears to be
affecting many Dell tablets and laptops. It also appears clear that the bug is
not present in 4.15.0-43.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rybu 1971 F pulseaudio
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f
InstallationDate: Installed on 2018-11-09 (81 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: Dell Inc. Latitude 5290 2-in-1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-44-generic N/A
linux-backports-modules-4.15.0-44-generic N/A
linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.15.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.3
dmi.board.name: 0M27Y3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 32
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5290 2-in-1
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-01-31 Thread overlord

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

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux-azure source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  Confirmed
Status in linux-hwe source package in Cosmic:
  New

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device

2019-01-31 Thread Xiao Feng Ren

I couldn't use the command apport-collect 1812822


root@:~# apport-collect 1812822
ERROR: The python-launchpadlib package is not installed. This functionality is 
not available.

root@:~# apt install python-launchpadlib -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-launchpadlib is already the newest version (1.10.3-3ubuntu0.1).
0 upgraded, 0 newly installed, 0 to remove and 41 not upgraded.

root@:~# dpkg -l python-launchpadlib
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture  Description
+++-=-=-=-
ii  python-launchpadl 1.10.3-3ubunt all   Launchpad web services client 
library


There's the guest log under /var/log/libvirt/qemu/kvm.log

2019-01-31 10:52:55.667+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.5~cloud0 (Openstack Ubuntu Testing Bot 
 Fri, 07 Sep 2018 04:25:04 +), qemu 
version: 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0), hostname: 
zfwcec178.boeblingen.de.ibm.com
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-s390x -name guest=kvm,debug-threads=on 
-S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-36-kvm/master-key.aes
 -machine s390-ccw-virtio-bionic,accel=kvm,usb=off,dump-guest-core=off -m 512 
-realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 
59f71b47-16e4-401d-9d33-30bc1605a84a -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-36-kvm/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -drive 
file=/root/xenial-minimal.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none
 -device 
virtio-blk-ccw,scsi=off,devno=fe.0.,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -chardev pty,id=charconsole0 -device 
sclpconsole,chardev=charconsole0,id=console0 -device 
virtio-balloon-ccw,id=balloon0,devno=fe.0.0001 -msg timestamp=on
2019-01-31 10:52:55.667+: Domain id=36 is tainted: high-privileges
2019-01-31T10:52:55.749009Z qemu-system-s390x: -chardev pty,id=charconsole0: 
char device redirected to /dev/pts/1 (label charconsole0)
TUNSETVNETLE ioctl() failed: File descriptor in bad state.
2019-01-31 10:57:29.694+: shutting down, reason=crashed

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

Title:
  Guest crashed when detaching the ovs interface device

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  New

Bug description:
  
   When detaching one openvswitch interface device with virsh detach-device, if 
the port has been deleted from the ovs and the interface device has been 
deleted. The virsh detach-device will fail with "error: Unable to read from 
monitor: Connection reset by peer", the qemu is terminated and the log shows " 
UNSETVNETLE ioctl() failed, File descriptor in bad state".  

  
  [Background] This error is originally found from the openstack KVM CI tempest 
test.  By investigating I found it's introduced by one ovs-vif patch, which 
deletes the ovs port and delete the interface before detaching the device.  You 
can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072

  
  Reproduced:

  
     root@:~#  ovs-vsctl del-port br0 tap9273235a-dd
     root@:~#  ip link del tap9273235a-dd

  
  The interface device tap9273235a-dd has been removed from the host(ifconfg, 
ovs-vsctl show)  and can be found in the guest.(logon the guest, ip a  it's in 
down state)

  
  root@:~# virsh detach-device kvm net.xml
  error: Failed to detach device from net.xml
  error: Unable to read from monitor: Connection reset by peer

  
  The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log
  TUNSETVNETLE ioctl() failed: File descriptor in bad state.
  2019-01-18 08:16:11.304+: shutting down, reason=crashed

  
  It seems the qemu tried to handle this interface, but in fact it has been 
deleted. qemu couldn't read the file and give the error.
  But I don't think the guest should be crashed directly for the file 
descriptor error. 



  
  Environment:
  Ubuntu 16.04.5 LTS
  Linux (EC12) 4.4.0-141-generic
  QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0)
  libvirtd (libvirt) 4.0.0


  
  net.xml

  
   
      
      
      
    
      
      
    
    
    
    
    


  
  kvm.xml

  
  
    kvm
    59f71b47-16e4-401d-9d33-30bc1605a84a
    524288
    524288
    1
    
      /machine
    
    
      hvm

[Kernel-packages] [Bug 1813934] Re: Vsock connect fails with ENODEV for large CID

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

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

Title:
  Vsock connect fails with ENODEV for large CID

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  - Problem Descripion:
  Kernel 4.19 introduced a bug in the Vsock protocol when using a large Context 
ID. 

  E.g.
  CID 0xfff000 works correctly but
  CID 0xfff001 fails with ENODEV when trying to connect to the listener.

  The issue now also shows up in Ubuntu 18.04 with 
   -> kernel 4.15.0-44-generic #47-Ubuntu 
  on x86_64 and s390x.

  It is already fixed upstream kernel by:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7fbe078c37aba3088359c9256c1a1d0c3e39ee81

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-01-31 Thread Adrian S.

I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and 
then using nvidia-settings or prime-select to set intel keeps the nvidia card 
on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch 
works.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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

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

[Kernel-packages] [Bug 1804481] Re: SecureBoot support for arm64

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

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

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

Title:
  SecureBoot support for arm64

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-meta package in Ubuntu:
  In Progress
Status in linux-signed package in Ubuntu:
  Fix Committed
Status in shim package in Ubuntu:
  Fix Released
Status in shim-signed package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-meta source package in Bionic:
  Triaged
Status in linux-signed source package in Bionic:
  Triaged
Status in shim source package in Bionic:
  Fix Released
Status in shim-signed source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux-meta source package in Cosmic:
  Triaged
Status in linux-signed source package in Cosmic:
  Triaged
Status in shim source package in Cosmic:
  Fix Released
Status in shim-signed source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Fix Committed
Status in linux-meta source package in Disco:
  In Progress
Status in linux-signed source package in Disco:
  Fix Committed
Status in shim source package in Disco:
  Fix Released
Status in shim-signed source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Ubuntu does not currently support SecureBoot for UEFI systems on arm64 
platforms.

  [Test Case]
  See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing

  [Fix]
  - Introduce shim-signed for arm64
  - Introduce grub-signed for arm64
  - Produce signed linux kernels

  [Regression Risk]
  We're enabling new signed packages - regressions would most likely fall into 
packaging issues.

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

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

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

** Changed in: linux-firmware (Ubuntu)
   Status: New => Fix Committed

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:00.0: Start 
IWL Error Log

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

2019-01-31 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

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

Title:
  Screen freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Screen freezes after wake up from suspend mode on Acer Aspire V3-571G.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 20:57:28 2019
  HibernationDevice: RESUME=UUID=a27531fc-cfed-43e8-a74e-35d79f38791c
  InstallationDate: Installed on 2018-08-26 (158 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=ef195b2c-8777-41a7-ba3d-9fcf3765739d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd12/04/2012:svnAcer:pnAspireV3-571G:pvrV2.09:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.09:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues

2019-01-31 Thread Marcelo Cerri

Marking linux-azure as invalid since the changes are being include on
the master kernels.

** Changed in: linux-azure (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Drivers: hv: vmbus: Offload the handling of channels to two workqueues

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  == SRU Justification ==

  Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs.  This 
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
  37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two 
workqueues")

  A second commit is also needed to prevent a deadlock with single NIC VMs.  
This commit is in mainline as of 4.19-rc3:
  e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in 
netvsc_probe()")

  The Disco development release has been rebased to upstream 4.19,  and
  it already has commit eceb0596548.  Disco only needs 37c2578c0c40.

  Cosmic does not require any dependent commits, just the two
  above(37c2578c0c40, e04e7a7bbd4b).

  linux-azure and Bionic(4.15+ kernels) require the following five dependent 
commits:
  4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF 
support")
  4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and 
sync")
  4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in 
vmbus_process_offer()")
  4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock 
earlier in netvsc_probe()")
  4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized 
channels")


  == Fixes ==
  ("Dependent commits mentioned above, based on Ubuntu release")

  e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier
  in netvsc_probe()")

  37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
  two workqueues")

  == Regression Potential ==
  Low.  Limited to hyperv.

  == Test Case ==

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

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

[Kernel-packages] [Bug 1802652] Re: keyboard backlight not working on Asus GM501

2019-01-31 Thread koen

Tried it, no change

drwxr-xr-x 74 root root 0 Jan 31 19:00 ..
lrwxrwxrwx  1 root root 0 Jan 31 19:00 asus::lightbar -> 
../../devices/platform/asus-nb-wmi/leds/asus::lightbar
lrwxrwxrwx  1 root root 0 Jan 31 19:03 asus-wireless::airplane -> 
../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input4::capslock -> 
../../devices/platform/i8042/serio0/input/input4/input4::capslock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input4::numlock -> 
../../devices/platform/i8042/serio0/input/input4/input4::numlock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input4::scrolllock -> 
../../devices/platform/i8042/serio0/input/input4/input4::scrolllock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input7::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::capslock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input7::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::compose
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input7::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::kana
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input7::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::numlock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input7::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::scrolllock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input8::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::capslock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input8::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::compose
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input8::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::kana
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input8::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::numlock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input8::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::scrolllock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input9::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::capslock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input9::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::compose
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input9::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::kana
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input9::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::numlock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 input9::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::scrolllock
lrwxrwxrwx  1 root root 0 Jan 31 19:03 phy0-led -> 
../../devices/pci:00/:00:14.3/leds/phy0-led


asus_wireless  20480  0
asus_nb_wmi28672  0
asus_wmi   28672  1 asus_nb_wmi
sparse_keymap  16384  1 asus_wmi
wmi28672  4 intel_wmi_thunderbolt,asus_wmi,wmi_bmof,mxm_wmi
video  49152  2 asus_wmi,i915


Was it on the same hardware @david?

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

Title:
  keyboard backlight not working on Asus GM501

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The keyboard lights and most of the F keys aren't working.
  Kernel = 4.15.0-20-generic
  System linux mint 19

  ls -hal /sys/class/leds/
  total 0
  drwxr-xr-x  2 root root 0 Nov 10 15:47 .
  drwxr-xr-x 72 root root 0 Nov 10 15:43 ..
  lrwxrwxrwx  1 root root 0 Nov 10 15:43 asus::lightbar -> 
../../devices/platform/asus-nb-wmi/leds/asus::lightbar
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 asus-wireless::airplane -> 
../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::capslock -> 
../../devices/platform/i8042/serio0/input/input4/input4::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::numlock -> 
../../devices/platform/i8042/serio0/input/input4/input4::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input4::scrolllock -> 
../../devices/platform/i8042/serio0/input/input4/input4::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::compose ->

[Kernel-packages] [Bug 1814151] [NEW] Screen freezes

2019-01-31 Thread Andrey Sorokin

Public bug reported:

Screen freezes after wake up from suspend mode on Acer Aspire V3-571G.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-44-generic 4.15.0-44.47
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrey 2549 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 31 20:57:28 2019
HibernationDevice: RESUME=UUID=a27531fc-cfed-43e8-a74e-35d79f38791c
InstallationDate: Installed on 2018-08-26 (158 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Acer Aspire V3-571G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=ef195b2c-8777-41a7-ba3d-9fcf3765739d ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-44-generic N/A
 linux-backports-modules-4.15.0-44-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.09
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd12/04/2012:svnAcer:pnAspireV3-571G:pvrV2.09:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.09:
dmi.product.family: Type1Family
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.09
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug bionic

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

Title:
  Screen freezes

Status in linux package in Ubuntu:
  New

Bug description:
  Screen freezes after wake up from suspend mode on Acer Aspire V3-571G.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2549 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 20:57:28 2019
  HibernationDevice: RESUME=UUID=a27531fc-cfed-43e8-a74e-35d79f38791c
  InstallationDate: Installed on 2018-08-26 (158 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=ef195b2c-8777-41a7-ba3d-9fcf3765739d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd12/04/2012:svnAcer:pnAspireV3-571G:pvrV2.09:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.09:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-01-31 Thread Marcelo Cerri

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

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

** Changed in: linux-azure (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Confirmed

** Changed in: linux-azure (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Bionic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1813796] Re: kernel bug null pointer dereference

2019-01-31 Thread DaveyPocket

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

Having the same issue with Dell XPS 9570 and Dell Thunderbolt dock.
Occasionally, connecting to dock AFTER system booted will not cause
crash. Going into suspend when connected to dock or disconnecting from
dock causes 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/1813796

Title:
  kernel bug null pointer dereference

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to linux-image-4.15.0-44-generic via the update
  manager today, I can't log in anymore. The login screen appears, but
  as soon as I've entered my password and hit enter, the desktop locks
  up, keyboard stops working and display goes black. Network is still
  working, so I could login remotely and see the crash live via
  journalctl. I attached the full output of journalctl -k -b -1

  In short it says

  BUG: unable to handle kernel NULL pointer dereference at 0245
  IP: intel_ddi_post_disable+0x54/0x170 [i915]
  PGD 0 P4D 0
  Oops:  [#1] SMP PTI

  Infos about my hardware:

  lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  apt-cache policy linux-image-4.15.0-44-generic
  linux-image-4.15.0-44-generic:
Installiert:   4.15.0-44.47
Installationskandidat: 4.15.0-44.47
Versionstabelle:
   *** 4.15.0-44.47 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Rebooting to the previous kernel 4.15.0-43 doesn't have this issue and
  I can login without issues.

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

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

[Kernel-packages] [Bug 400397] Re: Errors (hanging, only continue with Ctrl-c) while prosessing kexec-tools

2019-01-31 Thread dann frazier

** Bug watch added: Debian Bug tracker #891256
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256

** Also affects: kexec-tools (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891256
   Importance: Unknown
   Status: Unknown

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

Title:
  Errors (hanging,only continue with Ctrl-c) while prosessing kexec-
  tools

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools package in Debian:
  Unknown

Bug description:
  Karmic
  Binary package hint: kexec-tools

  jarkko@gandalf:/boot/grub$ sudo dpkg --configure -a -D2000
  Setting up kexec-tools (2009-2.0.0ubuntu10) ...
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin

   (hangs here forever) x

  ^Cdpkg: error processing kexec-tools (--configure):
   subprocess installed post-installation script killed by signal (Interrupt)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.31-3-generic
  Errors were encountered while processing:
   kexec-tools
  jarkko@gandalf:/boot/grub$

  Same thing with apt-get dist-upgrade.

  update-grub works when run alone;
  jarkko@gandalf:/boot/grub$ sudo update-grub 
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  Found kernel: /vmlinuz-2.6.31-3-generic
  Found kernel: /vmlinuz-2.6.31-2-generic
  Found kernel: /vmlinuz-2.6.31-1-generic
  Found kernel: /vmlinuz-2.6.30-10-generic
  Found kernel: /vmlinuz-2.6.30-9-generic
  Found kernel: /memtest86+.bin
  Updating /boot/grub/menu.lst ... done

  jarkko@gandalf:/boot/grub$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/400397/+subscriptions

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-01-31 Thread Joshua R. Poulson

Yes, please, per comment #8

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure

2019-01-31 Thread Joseph Salisbury

Commit b5679cebf780  is now in mainline as of v5.0-rc4

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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

[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure

2019-01-31 Thread Joshua R. Poulson

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

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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

[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-01-31 Thread Joshua R. Poulson

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

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

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

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

[Kernel-packages] [Bug 1814145] [NEW] laptop completely locks up on video/display changes

2019-01-31 Thread Barton Janes

Public bug reported:

Description:Ubuntu 18.04.1 LTS
Release:18.04
Package:linux-image-4.15.0-44-generic
Hardware:   Dell Precision 5530 with Dell Thunderbolt Dock

Latest round of updates added kernel 4.15.0-44.  On reboot the kernel
hangs the laptop, have to do a full hard shutdown then start. Laptop
will start and run fine when not docked. When docked to Dell Thunderbolt
dock with 2 external monitors connected by mini display port and HDMI
the laptop will lock up hard with any change to primary display.  If I
boot with laptop open and display running, laptop works fine unless I
try closing lid to use just the external displays, this will completely
lock up the system.  If I open system settings and re-arrange the
displays or change the primary display, the system will lock up hard.
Nothing is found in logs. Booting with the laptop closed not using the
laptop display, system will completely lock after logging into user
account.

The previous kernel, kernel 4.15.0-43 does not have this issue,
everything works fine, can re-arrange displays, hot dock and undock,
close lid to use only external displays, soft reboot and system does not
hang up or lock.

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

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

Title:
  laptop completely locks up on video/display changes

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Package:linux-image-4.15.0-44-generic
  Hardware:   Dell Precision 5530 with Dell Thunderbolt Dock

  Latest round of updates added kernel 4.15.0-44.  On reboot the kernel
  hangs the laptop, have to do a full hard shutdown then start. Laptop
  will start and run fine when not docked. When docked to Dell
  Thunderbolt dock with 2 external monitors connected by mini display
  port and HDMI the laptop will lock up hard with any change to primary
  display.  If I boot with laptop open and display running, laptop works
  fine unless I try closing lid to use just the external displays, this
  will completely lock up the system.  If I open system settings and re-
  arrange the displays or change the primary display, the system will
  lock up hard.  Nothing is found in logs. Booting with the laptop
  closed not using the laptop display, system will completely lock after
  logging into user account.

  The previous kernel, kernel 4.15.0-43 does not have this issue,
  everything works fine, can re-arrange displays, hot dock and undock,
  close lid to use only external displays, soft reboot and system does
  not hang up or lock.

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

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

[Kernel-packages] [Bug 1785198] Re: mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on Trusty

2019-01-31 Thread Kleber Sacilotto de Souza

** Also affects: linux (Ubuntu Trusty)
   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/1785198

Title:
  mkfs.vfat is causing multiple test failures in ubuntu_ltp_syscall on
  Trusty

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  New

Bug description:
  This test failed due to:
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  fallocate05 / fsync01 / msync04 / preadv03 / preadv03_64 / pwritev03 /
  pwrite03_64 / setxattr01 are failing with the same issue.

  The mkfs.vfat command only works once for the first test.

  So if you run the same test case (e.g. msync04) on a recently rebooted
  system, it will pass for the first run.

  <<>>
  tag=fallocate05 stime=1533288629
  cmdline="fallocate05"
  contacts=""
  analysis=exit
  <<>>
  tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0'
  incrementing stop
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:52: INFO: mkfs.btrfs does not exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1079: INFO: Testing on ext2
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext2 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext3
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext3 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  fallocate05.c:46: CONF: fallocate() not supported: EOPNOTSUPP
  tst_test.c:1079: INFO: Testing on ext4
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with ext4 opts='' extra opts=''
  mke2fs 1.42.9 (4-Feb-2014)
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on xfs
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts=''
  tst_test.c:1018: INFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:41: INFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:61: INFO: write(): ENOSPC
  fallocate05.c:62: PASS: write() wrote 8192 bytes
  fallocate05.c:71: PASS: fallocate() on full FS: ENOSPC
  fallocate05.c:80: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE)
  fallocate05.c:86: PASS: write()
  tst_test.c:1079: INFO: Testing on vfat
  tst_mkfs.c:83: INFO: Formatting /dev/loop0 with vfat opts='' extra opts=''
  mkfs.vfat: /dev/loop0 contains a mounted filesystem.
  tst_mkfs.c:94: BROK: mkfs.vfat:1: tst_test.c failed with 732

  Summary:
  passed   8
  failed   0
  skipped  2
  warnings 0
  <<>>
  initiation_status="ok"
  duration=8 termination_type=exited termination_id=2 corefile=no
  cutime=6 cstime=105
  <<>>
  INFO:

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

2019-01-31 Thread Gene Olson

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

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

Title:
  External monitors does not work anymore 4.15.0-44

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

Bug description:
  I am using a docking station for my laptop. After install the
  4.15.0-44 update my external monitors goes undetected after logging in
  or having the laptop closed.

  I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2)
  Graphics.

  Going back to the 4.15.0-43 version makes it all work fine again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  2407 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4
  InstallationDate: Installed on 2018-10-17 (103 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20HF004MMX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF004MMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF004MMX
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

2019-01-31 Thread Dave Chiluk

Yah @jparedes you should probably open a different bug.  You are running
into something different.

I've also verified that this is now 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/1813663

Title:
  External monitors does not work anymore 4.15.0-44

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

Bug description:
  I am using a docking station for my laptop. After install the
  4.15.0-44 update my external monitors goes undetected after logging in
  or having the laptop closed.

  I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2)
  Graphics.

  Going back to the 4.15.0-43 version makes it all work fine again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  2407 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4
  InstallationDate: Installed on 2018-10-17 (103 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20HF004MMX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF004MMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF004MMX
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker