date:20190130

Thanks. That's definitely a kernel bug (or a hardware fault, but let's
hope a kernel bug).

I can now finally hand this over to the kernel people. Although it might
also be helpful if you report the bug upstream here:

  https://bugzilla.kernel.org/enter_bug.cgi

with a new title like:

  "i915 reports a nonexistent LVDS output (as connected and on)"

and the details:

grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected
grep . /sys/class/drm/*/dpms
   /sys/class/drm/card0-LVDS-1/dpms:On
   /sys/class/drm/card0-VGA-1/dpms:On

then tell us the new bug ID.

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

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

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

$ uname -r
   4.20.0-042000-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected




** Attachment added: "journalctl -b -0 > 19.04_boot_4.20.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+attachment/5234514/+files/19.04_boot_4.20.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:
  Incomplete

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 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)

$ uname -r
   5.0.0-05rc4-generic
grep . /sys/class/drm/*/enabled
   /sys/class/drm/card0-LVDS-1/enabled:enabled
   /sys/class/drm/card0-VGA-1/enabled:enabled
grep . /sys/class/drm/*/status
   /sys/class/drm/card0-LVDS-1/status:connected
   /sys/class/drm/card0-VGA-1/status:connected

** Attachment added: "journalctl -b -1 > 19.04_boot_5.0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+attachment/5234516/+files/19.04_boot_5.0.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:
  Incomplete

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 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)

** Attachment added: "journalctl -b -1 > 19.04_boot_4.20_1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+attachment/5234515/+files/19.04_boot_4.20_1.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:
  Incomplete

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 1813664] Re: linux: 4.19.0-12.13 -proposed tracker

2019-01-30 Thread Brad Figg

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** 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: 
  derivatives:
  -- swm properties --
  phase: Testing
  phase-changed: Tuesday, 29. January 2019 16:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress
regression-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/1813664

Title:
  linux: 4.19.0-12.13 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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: 
  derivatives:
  -- swm properties --
  phase: Testing
  phase-changed: Tuesday, 29. January 2019 16:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

2019-01-30 Thread David

Try:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/comments/34
?

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

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

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  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.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-30 Thread David

Try:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/comments/34
?

-- 
You 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 -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input7::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::capslock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::compose -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::kana -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::numlock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 input8::scrolllock -> 
../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock
  lrwxrwxrwx  1 root root 0 Nov 10 15:47 phy0-led -> 
../../devices/pci:00/:00:14.3/leds/phy0-led

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

Oops. Please also run this:

grep . /sys/class/drm/*/status

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

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 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)

Thanks. Please test v5.0 too, and then that's enough.

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

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 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)

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

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

** Attachment added: "19.04_boot_4.19.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+attachment/5234498/+files/19.04_boot_4.19.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:
  Incomplete

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 1814015] Status changed to Confirmed

This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1814015] Re: After upgrade to kernel .44 docking station and external monitors not working

2019-01-30 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (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/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 1814015] [NEW] After upgrade to kernel .44 docking station and external monitors not working

You have been subscribed to a public bug:

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:

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


** Tags: amd64 apport-bug artful2bionic bionic dist-upgrade third-party-packages
-- 
After upgrade to kernel .44 docking station and external monitors not working
https://bugs.launchpad.net/bugs/1814015
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 1806039] Re: Touchpad not showing in /proc/bus/input/devices

[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/1806039

Title:
  Touchpad not showing in /proc/bus/input/devices

Status in linux package in Ubuntu:
  Expired

Bug description:
  Device: Acer A114-32-P34S
  Touchpad type: Unknown
  Working on Windows

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

Generally for each version you try you need to install all the packages
_except_ the "lowlatency" ones.

So:

  linux-headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb
  linux-headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  
linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Incomplete

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 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)

If I consider 4.19, then which of these files I need to install,

  linux-headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb
  linux-headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-headers-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb
  
linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  
linux-image-unsigned-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
  linux-modules-4.19.0-041900-lowlatency_4.19.0-041900.201810221809_amd64.deb

For currently installed 19.04,
  uname -r
  4.18.0-11-generic

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

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 1813928] Re: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

2019-01-30 Thread Kai-Heng Feng

Would it be possible for you to test the proposed kernel and post back if it 
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to 
enable and use -proposed.

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

Title:
  kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  just happened in the background ... no idea about the direct cause

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hnl1417 F...m pulseaudio
   /dev/snd/controlC0:  hnl1417 F pulseaudio
  Date: Wed Jan 30 20:57:49 2019
  Failure: oops
  HibernationDevice: RESUME=UUID=5835e245-0f6b-49d1-8d73-f7d80ed579cb
  InstallationDate: Installed on 2018-11-14 (76 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 23252F0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/xubuntu--vg-root 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: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23252F0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 100010263594
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn23252F0:pvrThinkPadX230:rvnLENOVO:rn23252F0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23252F0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad

2019-01-30 Thread Terry Rudd

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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)

Next, please try some newer kernels (you only have kernel 4.18 with
Ubuntu 19.04) from here:

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

and then use the simple test of:

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

to tell us if a newer kernel has changed things.

** 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/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:
  Incomplete

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 1813701] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

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

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  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] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/1813701/+subscriptions

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

[Kernel-packages] [Bug 1813957] Re: T480: closed lid and touchpad

2019-01-30 Thread Anthony Wong

There is a newer linux kernel in -proposed pocket released today with
version 4.15.0-45.48, please give it a try.

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813902] Re: Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

2019-01-30 Thread Anthony Wong

There is a newer linux kernel in -proposed pocket released today with
version 4.15.0-45.48, should have fixed your problem, please give it a
try.

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

Title:
  Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  When notebook is in docking station the kernel crashes after bootup and logon 
in GDM.
  If notebook is in standalone mode without any external devices connected 
everything works.

  Tried to step back to Kernel 4.15.0-43-generic and everything works
  like a charm.

  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:
Installed: 4.15.0-44.47
Candidate: 4.15.0-44.47
Version table:
   *** 4.15.0-44.47 500
  500 http://at.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

  
  /var/log/syslog reports a Kernel BUG...
  Jan 30 10:18:41 bexlt036 kernel: [   34.993161] BUG: unable to handle kernel 
NULL pointer dereference at 0245
  Jan 30 10:18:41 bexlt036 kernel: [   34.993215] IP: 
intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993217] PGD 0 P4D 0 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993222] Oops:  [#1] SMP PTI
  Jan 30 10:18:41 bexlt036 kernel: [   34.993225] Modules linked in: ccm 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep btusb 
btrtl btbcm cdc_mbim btintel cdc_wdm bluetooth cdc_ncm usbnet uvcvideo cdc_acm 
mii ecdh_generic joydev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek 
snd_hda_codec_generic irqbypass snd_hda_intel intel_cstate snd_hda_codec 
intel_rapl_perf snd_hda_core snd_hwdep thinkpad_acpi snd_pcm nvram rmi_smbus 
iwlmvm rmi_core input_leds videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
mac80211 snd_seq_midi
  Jan 30 10:18:41 bexlt036 kernel: [   34.993282]  videobuf2_core serio_raw 
videodev snd_seq_midi_event media iwlwifi snd_rawmidi wmi_bmof snd_seq 
rtsx_pci_ms memstick snd_seq_device cfg80211 snd_timer snd mei_me soundcore mei 
mac_hid lpc_ich shpchp ie31200_edac sch_fq_codel sunrpc parport_pc ppdev lp 
parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt 
hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i915 ahci aesni_intel 
i2c_algo_bit e1000e aes_x86_64 drm_kms_helper crypto_simd glue_helper cryptd 
psmouse syscopyarea libahci sysfillrect sysimgblt fb_sys_fops drm ptp i2c_i801 
rtsx_pci pps_core wmi video
  Jan 30 10:18:41 bexlt036 kernel: [   34.993339] CPU: 2 PID: 2890 Comm: Xorg 
Not tainted 4.15.0-44-generic #47-Ubuntu
  Jan 30 10:18:41 bexlt036 kernel: [   34.993341] Hardware name: LENOVO 
20BE00B5GE/20BE00B5GE, BIOS GMET66WW (2.14 ) 07/01/2014
  Jan 30 10:18:41 bexlt036 kernel: [   34.993375] RIP: 
0010:intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993377] RSP: 0018:a739c28ef9f0 
EFLAGS: 00010297
  Jan 30 10:18:41 bexlt036 kernel: [   34.993380] RAX: 0007 RBX: 
95550026e000 RCX: c054f272
  Jan 30 10:18:41 bexlt036 kernel: [   34.993383] RDX:  RSI: 
 RDI: 95550026e000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993385] RBP: a739c28efa20 R08: 
 R09: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993387] R10: 0047 R11: 
028f R12: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993390] R13: 95550026e000 R14: 
9554ffef8000 R15: 9554ffa62000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993393] FS:  7fbfc6b5b600() 
GS:95551e28() knlGS:
  Jan 30 10:18:41 bexlt036 kernel: [   34.993395] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 30 10:18:41 bexlt036 kernel: [   34.993398] CR2: 0245 CR3: 
0003bc132003 CR4: 001606e0
  Jan 30 10:18:41 bexlt036 kernel: [   34.993400] Call Trace:
  Jan 30 10:18:41 bexlt036 kernel: [   34.993432]  ? 
intel_dp_sink_dpms+0xbb/0xf0 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993462]  
intel_mst_post_disable_dp+0x99/0xd0 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993494]  
intel_encoders_post_disable.isra.102+0x66/0x80 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993523]  
haswell_crtc_disable+0xe8/0x150 [i915]
  Jan 30 10:18:41

[Kernel-packages] [Bug 1812359] Re: No login screen displayed on a NETBOX nT-435/535

Great! I think I understand the problem now.

The problem is that the Linux kernel is telling us there are two
displays:

  LVDS - a laptop display that does not exist
  VGA - your real monitor

And then due to bug 1760849, gdm3 is putting the login screen on that
laptop display which doesn't really exist.

A fix for bug 1760849 would suffice. But let's keep this bug open and
make this bug just about the kernel bug of reporting an LVDS output
which doesn't exist.

** Summary changed:

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

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

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

** No longer affects: gdm3 (Ubuntu)

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

** Description changed:

- I've tried the solution mentioned here
- https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72
- but it did not solve my issue.
+ 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.
+  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
+  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)

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

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:

[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

** Summary changed:

- [amdgpu] Flickering graphics corruption in kernel 4.18.0-13.14-generic 
4.18.17 (but none observed in kernel 4.18.0-10)
+ [amdgpu] Flickering graphics corruption (but none observed in kernels 
4.18.10-4.18.12)

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => 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/1813701

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  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] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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/1813701/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

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

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

** Tags added: regression-update

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

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => 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/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 Committed

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 1812359] [NEW] No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)

You have been subscribed to a public bug:

I've tried the solution mentioned here
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/comments/72
but it did not solve my issue.

$ 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)

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

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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


** Tags: amd64 apport-bug bionic multimonitor
-- 
No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output 
which does not exist as connected and on)
https://bugs.launchpad.net/bugs/1812359
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 1812014] Re: keyboard not responding after suspend after some time

Thanks. The best guess I can make is a problem in upower or the Nvidia
driver (comment #15). Those are definitely performance problems (100%
CPU for no obvious reason) and could well explain why the keyboard stops
responding.

Maybe next we need to look at the system log in detail... If you can
recover from the problem without rebooting then please run:

  journalctl -b0 > curlog.txt

If you have to reboot to recover from the problem then please run this
after rebooting:

  journalctl -b-1 > prevlog.txt

and send us the resulting log file.

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

Title:
  keyboard not responding after suspend after some time

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I work on Lenovo laptop y-700. When I resume system after suspend, keyboards 
stop working, and sometimes there are performance problems visible when playing 
videos. It happens not immediately but after a few minutes or even a few hours 
of working. Restart or shutdown does not finish correctly and I need to hold 
the power button for a few seconds.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-08-06 (165 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1812356] Re: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low

Triaged as a systemd issue per
https://gitlab.freedesktop.org/libinput/libinput/issues/232

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

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

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

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

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

Title:
  AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low

Status in libinput package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.freedesktop.org/libinput/libinput/issues/232

  ---

  While moving pointer (cursor) using Touchpad, vertical movement is
  very slow and short (= less velocity and less acceleration compared to
  horizontal axis). Horizontal movement is fine. So, when circle is
  drawn on the Touchpad, the pointer moves in oval shape.

  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/controlC1:  user   1168 F pulseaudio
   /dev/snd/controlC0:  user   1168 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 10:10:35 2019
  HibernationDevice: RESUME=UUID=5eb56af0-cec9-43d4-b84a-46d561cecb30
  InstallationDate: Installed on 2019-01-13 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80N4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a791b794-48c2-47fb-b2e6-11085529d9ba ro quiet splash vt.handoff=1
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: Lenovo
  dmi.bios.version: BDCN71WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-14IBD
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-14IBD
  dmi.modalias: 
dmi:bvnLenovo:bvrBDCN71WW:bd08/03/2016:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80N4
  dmi.product.version: Lenovo Yoga 500-14IBD
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back (amdgpu kernel crash?)

** Summary changed:

- Ubuntu  18.10 After Blank Screen System Won't Come Back
+ Ubuntu  18.10 After Blank Screen System Won't Come Back (amdgpu kernel crash?)

** Summary changed:

- Ubuntu  18.10 After Blank Screen System Won't Come Back (amdgpu kernel crash?)
+ Ubuntu 18.10 After Blank Screen System Won't Come Back (amdgpu kernel crash?)

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

Title:
  Ubuntu 18.10 After Blank Screen System Won't Come Back (amdgpu kernel
  crash?)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.10 if the blank screen feature initiates (5 minutes
  default) the system will remain blank and there is no way to get the
  display back on without a hard reset. The video card I am using is a
  Vega 64. Other users who have Vega AMD GPU's are experiencing the same
  issue. This is only happening in Ubuntu 18.10. Does not occur in my
  Arch or Fedora installs.

  To reproduce:
  - Let 'Blank Screen' feature execute (5 min default)
  - Screen will not come back

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  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 Oct 25 10:18:59 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] 
[1002:687f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4]
  InstallationDate: Installed on 2018-10-19 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Micro-Star International Co., Ltd. MS-7B78
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X470 GAMING PRO CARBON (MS-7B78)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B78
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  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
  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/1799964/+subscriptions

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

[Kernel-packages] [Bug 1813956] Re: Lenovo T480: problem with external screens

2019-01-30 Thread Anthony Wong

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

Title:
  Lenovo T480: problem with external screens

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup: two external screens connected through separate DP ports and a
  docking station to a laptop Lenovo T480

  When the laptop is launched in the docking station (lid is closed) the 
screens remain off (there is information about missing signal).
  When the laptop is launched out of docking station (using only the internal 
screen), after logging to the Gnome session, connecting to the docking station: 
there is an image on two external screens. However, once the laptop is 
suspended or screensaver enabled (switch off all screens), after wakeup, all 
screens remain off.

  This bug is 4.15.0-44 kernel specific. With the previous version
  4.15.0-43 the external screens were served properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:27:50 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2019-01-30 Thread ALinuxUser

Me again. Now, I might have faulty hardware, but it occured to me that
having 'reboot=w' in my kernel boot arguments might be the problem. I
will test - i.e. see whether the patch works if I remove that argument -
when I have time. Still, using that argument does have a purpose

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB

[Kernel-packages] [Bug 1813999] Re: ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

2019-01-30 Thread Terry Rudd

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

Title:
ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

Status in linux package in Ubuntu:
Confirmed

Bug description:
This problem appeared on the first boot Linux 4.15.0-44, and was not
present in previous kernels, including 4.15.0-43. The problem occurs
every time with 4.15.0-44. Since the problem occurred, 4.15.0-43
continues to work w/o issues. The log should show multiple boots with
both kernels, both Xorg and Wayland.

The problem occurs wheen connecting a TB-16 dock-connected external
display, or when plugging in a TB-16 dock-connected external display
during an X session. The symptoms are different with Xorg and
Wayland, but both cause kernel exceptions. With Xorg the system
freezes up, but will still ping. With Wayland the display goes black,
but userland is still accessible. With Xorg the system is gone before
the Login screen appears. With Wayland the login screen is okay, but
the problem occurs immediately after a successful login. The system
runs normally with both Xorg and Wayland so long as the external
display is not connected.

The problem does not occur if the display is plugged in through a USBc
(non-ThunderBolt) port.

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gene 1982 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 30 16:49:20 2019
HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
InstallationDate: Installed on 2018-11-19 (72 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: Dell Inc. XPS 15 9570
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0
mem_sleep_default=deep
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/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 02MJVY
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.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.sys.vendor: Dell Inc.

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

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

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

This change was made by a bot.

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

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

Title:
  Mounting certain LVM2 LV fails with "Structure needs cleaning"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  REGRESSION.

  Per the reports from others as well in
   and
  , some LVM2 LVs are failing to mount with the
  error:

  mount(2) system call failed: Structure needs cleaning.

  e2fsck -f reports things are fine.

  Reverting my kernel package from linux-image-4.15.0-44-generic to
  linux-image-4.15.0-43-generic solved the problem for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Wed Jan 30 19:21:13 2019
  HibernationDevice: RESUME=UUID=0925b709-2477-4f37-8207-0313728c5c68
  InstallationDate: Installed on 2012-08-18 (2356 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/diskvg-ubuntu_root_lv ro
  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-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (256 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99X EVO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd11/25/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1813936] Re: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

2019-01-30 Thread Terry Rudd

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

** This bug has been marked a duplicate of bug 1813928
   kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

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

Title:
  kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  happend during normal operation in the background

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hnl1417 F...m pulseaudio
   /dev/snd/controlC0:  hnl1417 F pulseaudio
  Date: Wed Jan 30 21:56:47 2019
  Failure: oops
  HibernationDevice: RESUME=UUID=5835e245-0f6b-49d1-8d73-f7d80ed579cb
  InstallationDate: Installed on 2018-11-14 (76 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 23252F0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/xubuntu--vg-root 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: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at /build/linux-A9GvNk/linux-4.15.0/lib/string.c:1052!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23252F0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 100010263594
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB0WW(2.70):bd09/25/2017:svnLENOVO:pn23252F0:pvrThinkPadX230:rvnLENOVO:rn23252F0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 23252F0
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1813820] Re: Waking from Suspend causes screen to appear with grey static (like a TV with no signal)

2019-01-30 Thread Craig Stein

$ uname -a
Linux craig-Predator-PH517-61 5.0.0-05rc4-generic #201901272036 SMP Mon Jan 
28 01:38:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Suspend to ram still results in gibberish on the screen with the latest
upstream kernel. Confirmed bug and added tag kernel-bug-exists-upstream.

Please let me know what steps to take next.

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

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

Title:
  Waking from Suspend causes screen to appear with grey static (like a
  TV with no signal)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running Kubuntu 18.10. This is the PH517-61 Acer Predator Helios
  500 with the Ryzen processor. My first issue I need to deal with is
  Suspend. I have temporarily disabled suspend in the kcmshell5
  configuration. If I do let the laptop suspend and then hit the
  keyboard I get what appears to be a 1950s TV with no signal. At this
  point I manually power down and then power up again and am able to
  view things on screen.

  Running these commands I get this information:
  $ journalctl -b -g suspend
  Compiled without pattern matching support

  $ journalctl -b -p3
  -- Logs begin at Sun 2019-01-27 22:00:42 CST, end at Mon 2019-01-28 21:01:54 
CST. --
  Jan 28 20:40:33 craig-Predator-PH517-61 kernel: tpm_crb MSFT0101:00: can't 
request region for resource [mem 0xdf775000-0xdf778fff]
  Jan 28 20:40:42 craig-Predator-PH517-61 spice-vdagent[2100]: Cannot access 
vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

  $ uname -a
  Linux craig-Predator-PH517-61 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 
09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  This is a Vega 56 card but Kubuntu seems to think it is a Vega 64:
  $ lspci -k | grep -EA3 'VGA|3D|Display'
  08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Vega 10 XT [Radeon RX Vega 64] (rev c7)
  Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64]
  Kernel driver in use: amdgpu
  Kernel modules: amdgpu

  $ glxinfo | grep "OpenGL version"
  OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2

  I will attempt to flesh this out more when I get home.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  craig  2094 F pulseaudio
   /dev/snd/controlC0:  craig  2094 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-01-28 (1 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Acer Predator PH517-61
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=5f69d6c1-716a-41ac-a88c-b271a71ce5a0 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/12/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Cayman_PRS
  dmi.board.vendor: PRS
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd10/12/2018:svnAcer:pnPredatorPH517-61:pvrV1.07:rvnPRS:rnCayman_PRS:rvrV1.07:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Predator Helios 500
  dmi.product.name: Predator PH517-61
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1814009] [NEW] Mounting certain LVM2 LV fails with "Structure needs cleaning"

2019-01-30 Thread frank

Public bug reported:

REGRESSION.

Per the reports from others as well in
 and
,
some LVM2 LVs are failing to mount with the error:

mount(2) system call failed: Structure needs cleaning.

e2fsck -f reports things are fine.

Reverting my kernel package from linux-image-4.15.0-44-generic to linux-
image-4.15.0-43-generic solved the problem for me.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-44-generic (not installed)
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
Date: Wed Jan 30 19:21:13 2019
HibernationDevice: RESUME=UUID=0925b709-2477-4f37-8207-0313728c5c68
InstallationDate: Installed on 2012-08-18 (2356 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/diskvg-ubuntu_root_lv ro
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-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.3
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-05-20 (256 days ago)
WifiSyslog:
 
dmi.bios.date: 11/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2201
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd11/25/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

Title:
  Mounting certain LVM2 LV fails with "Structure needs cleaning"

Status in linux package in Ubuntu:
  New

Bug description:
  REGRESSION.

  Per the reports from others as well in
   and
  , some LVM2 LVs are failing to mount with the
  error:

  mount(2) system call failed: Structure needs cleaning.

  e2fsck -f reports things are fine.

  Reverting my kernel package from linux-image-4.15.0-44-generic to
  linux-image-4.15.0-43-generic solved the problem for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', 
'/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Wed Jan 30 19:21:13 2019
  HibernationDevice: RESUME=UUID=0925b709-2477-4f37-8207-0313728c5c68
  InstallationDate: Installed on 2012-08-18 (2356 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise

[Kernel-packages] [Bug 1609143] Re: "lsluns" does not display ds8k lun information and unable to activate ds8k storage luns in host

2019-01-30 Thread bugproxy

** Tags removed: targetmilestone-inin16041
** Tags added: targetmilestone-inin---

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

Title:
  "lsluns" does not display ds8k lun information and unable to activate
  ds8k storage luns in host

Status in Ubuntu on IBM z Systems:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  == Comment: #2 - Steffen Maier  - 2016-08-01 09:54:09 ==
  While 

  LTC bug 139096 - LP1567602 : FCP devices are not detected correctly
  nor deterministically

  did successfully fix the attachment of "regular" LUNs of (peripheral device) 
type disk,
  it seems the attachment of the (report luns) WLUN 0xc101 (49409) 
still shows issues with the ALUA device handler:

  [  105.049479] scsi 0:0:7:49409: Well-known LUNIBM  2107900  
.470 PQ: 0 ANSI: 5
  [  105.050109] scsi 0:0:7:49409: alua: disable for non-disk devices
  [  105.050112] scsi 0:0:7:49409: alua: Attach failed (-22)
  [  105.050114] scsi 0:0:7:49409: failed to add device handler: -22

  After this failed attempt to attach such LUN (here triggered by the
  "lsluns" tool from s390-tools to discover LUNs from out of user
  space), the corresponding SCSI device is INvisible from user space,
  but still exists in-kernel in some broken state.

  In our case here, the attachment should have been successful
  (or the scsi_device been unregistered completely in maybe other cases).

  On the next attempt to run lsluns against the same target remote port
  and thus the same WLUN SCSI device, we get the following kernel
  warning as a follow-on error:

  [  572.079588] scsi 0:0:7:49409: Well-known LUNIBM  2107900  
.470 PQ: 0 ANSI: 5
  [  572.080354] sysfs: cannot create duplicate filename 
'/bus/scsi/devices/0:0:7:49409'
  [  572.080380] [ cut here ]
  [  572.080381] WARNING: at /build/linux-0ECIDW/linux-4.4.0/fs/sysfs/dir.c:31
  [  572.080381] Modules linked in: qeth_l3 chsc_sch eadm_sch qeth ccwgroup 
ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs 
zlib_deflate raid10 raid456 async_memcpy async_raid6_recov async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_round_robin ghash_s390 
prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common 
dasd_eckd_mod dasd_mod zfcp qdio scsi_transport_fc scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath
  [  572.080404] CPU: 1 PID: 8494 Comm: sh Not tainted 4.4.0-31-generic 
#50-Ubuntu
  [  572.080405] task: 0001d7740af0 ti: 0001d8144000 task.ti: 
0001d8144000
  [  572.080406] Krnl PSW : 0704c0018000 003a35fc 
(sysfs_warn_dup+0x7c/0x98)
  [  572.080415]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 
EA:3
 Krnl GPRS: 00cf7034 0006 0047 

  [  572.080417]003a35f8 02c6 0001da805400 
0001d8f2f178
  [  572.080417]00c1d0e0 0001e8cd3ab8 0001 
0001e8cd3ab8
  [  572.080418]0001d8cac4b0 7b7c8000 003a35f8 
0001d81479b8
  [  572.080425] Krnl Code: 003a35ec: c020002f33f3larl
%r2,989dd2
003a35f2: c0e5fff6bf0bbrasl   
%r14,27b408
   #003a35f8: a7f40001brc 
15,3a35fa
   >003a35fc: b904002dlgr 
%r2,%r13
003a3600: ebbff0a4lmg 
%r11,%r15,160(%r15)
003a3606: c0f4fffa5999brcl
15,2ee938
003a360c: a739lghi%r3,0
003a3610: a7f4ffecbrc 
15,3a35e8
  [  572.080438] Call Trace:
  [  572.080440] ([<003a35f8>] sysfs_warn_dup+0x78/0x98)
  [  572.080443]  [<003a3b10>] sysfs_do_create_link_sd.isra.0+0xf8/0x108
  [  572.080447]  [<005c4004>] bus_add_device+0x13c/0x230
  [  572.080448]  [<005c1718>] device_add+0x398/0x680
  [  572.080453]  [<005f79bc>] scsi_sysfs_add_sdev+0xcc/0x2a8
  [  572.080456]  [<005f4198>] scsi_probe_and_add_lun+0xcc0/0xe18
  [  572.080457]  [<005f4be2>] __scsi_scan_target+0xba/0x268
  [  572.080458]  [<005f4e92>] scsi_scan_target+0x102/0x120
  [  572.080468]  [<03ff800765f6>] zfcp_unit_scsi_scan+0x7e/0x90 [zfcp]
  [  572.080471]  [<03ff80076948>] zfcp_unit_add+0x168/0x1f0 [zfcp]
  [  572.080474]  [<03ff80075564>] zfcp_sysfs_unit_add_store+0x54/0x70 
[zfcp]
  [  572.080476]  [<003a1d7a>] kernfs_fop_write+0x13a/0x190
  [  572.080480]  [<0030fc94>] vfs_write+0x94/0x1a0
  [

[Kernel-packages] [Bug 1813831] Re: Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

2019-01-30 Thread Andy Fuchs

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

Same here. Using Lenovo T560 with docking station and two screens
(DVI/VGA).

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

Title:
  Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 LTS on a HP EliteBook 840 G5 with docking station 
and two screens attached via DisplayPort.
  Reproducibly, when I close the lid of my notebook, the kernel 
4.15.0-44.47-generic crashes with a Oops in i915 / intel_ddi_post_disable.
  The previous kernel 4.15.0-43.46-generic works without problems.

  Oops:

  [  224.498572] BUG: unable to handle kernel NULL pointer dereference at 
0245
  [  224.498658] IP: intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498663] PGD 0 P4D 0 
  [  224.498672] Oops:  [#1] SMP PTI
  [  224.498677] Modules linked in: hid_logitech_hidpp hid_logitech_dj 
hid_cherry usbhid rfcomm nfnetlink xfrm_user xfrm_algo xt_addrtype overlay aufs 
wireguard(OE) ip6_udp_tunnel udp_tunnel thunderbolt ccm xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
ipt_REJECT nf_reject_ipv4 xt_tcpudp devlink ebtable_filter ebtables bnep 
nls_iso8859_1 hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_hda_codec_conexant snd_hda_codec_generic 
snd_pcm_dmaengine arc4 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi iwlmvm mac80211 intel_rapl
  [  224.498761]  x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi 
kvm_intel snd_seq kvm irqbypass intel_cstate hp_wmi intel_rapl_perf cfg80211 
sparse_keymap intel_wmi_thunderbolt joydev input_leds snd_seq_device serio_raw 
wmi_bmof snd_timer snd soundcore uvcvideo videobuf2_vmalloc btusb 
videobuf2_memops btrtl videobuf2_v4l2 btbcm videobuf2_core btintel videodev 
media bluetooth ecdh_generic shpchp mei_me mei ucsi_acpi typec_ucsi idma64 
typec virt_dma intel_lpss_pci processor_thermal_device intel_pch_thermal 
intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone mac_hid 
int3400_thermal acpi_pad acpi_thermal_rel hp_wireless sch_fq_codel 
iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc 
arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher
  [  224.498851]  af_alg dm_crypt crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel i915 aes_x86_64 crypto_simd glue_helper 
cryptd e1000e ptp i2c_algo_bit pps_core drm_kms_helper psmouse syscopyarea 
sysfillrect sysimgblt fb_sys_fops nvme nvme_core drm i2c_i801 i2c_hid wmi hid 
video pinctrl_sunrisepoint
  [  224.498895] CPU: 0 PID: 1952 Comm: Xorg Tainted: G   OE
4.15.0-44-generic #47-Ubuntu
  [  224.498899] Hardware name: HP HP EliteBook 840 G5/83B2, BIOS Q78 Ver. 
01.04.00 09/12/2018
  [  224.498961] RIP: 0010:intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498966] RSP: 0018:bf5cc45ab9f0 EFLAGS: 00010297
  [  224.498971] RAX: 0007 RBX: 9803af6ff000 RCX: 
c0744272
  [  224.498974] RDX:  RSI:  RDI: 
9803af6ff000
  [  224.498978] RBP: bf5cc45aba20 R08: 0003 R09: 

  [  224.498982] R10: 0209 R11: 0170 R12: 

  [  224.498985] R13: 9803af6ff000 R14: 9803aed9 R15: 
98031202d000
  [  224.498991] FS:  7ff14e363600() GS:9803df40() 
knlGS:
  [  224.498995] CS:  0010 DS:  ES:  CR0: 80050033
  [  224.498999] CR2: 0245 CR3: 000830496006 CR4: 
003606f0
  [  224.499002] Call Trace:
  [  224.499064]  ? intel_dp_sink_dpms+0xbb/0xf0 [i915]
  [  224.499118]  intel_mst_post_disable_dp+0x99/0xd0 [i915]
  [  224.499175]  intel_encoders_post_disable.isra.102+0x66/0x80 [i915]
  [  224.499226]  haswell_crtc_disable+0xe8/0x150 [i915]
  [  224.499280]  intel_atomic_commit_tail+0x7ea/0xd30 [i915]
  [  224.499330]  intel_atomic_commit+0x277/0x2b0 [i915]
  [  224.499367]  drm_atomic_commit+0x51/0x60 [drm]
  [  224.499387]  drm_atomic_helper_set_config+0x7c/0x90 [drm_kms_helper]
  [  224.499414]  __drm_mode_set_config_internal+0x6b/0x120 [drm]
  [  224.499440]  drm_mode_setcrtc+0x47f/0x660 [drm]
  [  224.499464]  ? drm_mode_getcrtc+0x190/0x190 [drm]
  [  224.499486]  drm_ioctl_kernel+0x5f/0xb0 [drm]
  [  224.499507]  drm_ioctl+0x31b/0x3d0 [drm]
  [  224.499528]  ? drm_mode_getcrtc+0x190/0x190 [drm]

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

This change was made by a bot.

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

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

Title:
  kernel BUG at fs/ext4/inode.c:2679!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I started seeing this bug in Ubuntu 18.04 running VMWare Workstation
  Pro 14. After upgrading to Ubuntu 18.10 and VMware Workstation 15 the
  bug still appears. I started to ask questions on the VMware Community,
  https://communities.vmware.com/thread/604705. Because I had some
  additional time to troubleshoot I am also noticing that this bug is
  being reported on other Linux Distributions notably:
  https://bugzilla.redhat.com/show_bug.cgi?id=1662314

  Conditions to reproduce. Laptop is running 2 NVMe drives with Cryptfs
  on each drive (unsure if this is related). Running Vmware Workstation
  Pro 15 with a Windows 10 Guest upon shutting down the Windows Guest a
  kernel stack strace appears in both dmesg -w and /var/log/syslog. The
  VM does not gracefully stop.

  Stack Trace is Below:

  Jan 30 17:10:02 system-box kernel: [13117.565550] [ cut
  here ]

  Jan 30 17:10:02 system-box kernel: [13116.565552] kernel BUG at
  fs/ext4/inode.c:2679!

  Jan 30 17:10:02 system-box kernel: [13117.565558] invalid opcode: 
  [#1] SMP PTI

  Jan 30 17:10:02 system-box kernel: [13117.565561] CPU: 0 PID: 18820
  Comm: kworker/u8:0 Tainted: GW  OE 4.18.0-13-generic
  #14-Ubuntu

  Jan 30 17:10:02 system-box kernel: [13117.565562] Hardware name:
  LENOVO 20HES35Q00/20HES35Q00, BIOS N1QET79W (1.54 ) 11/16/2018

  Jan 30 17:10:02 system-box kernel: [13117.565566] Workqueue: writeback
  wb_workfn (flush-253:3)

  Jan 30 17:10:02 system-box kernel: [13117.565569] RIP:
  0010:mpage_prepare_extent_to_map+0x2bc/0x2f0

  Jan 30 17:10:02 system-box kernel: [13117.565570] Code: 86 0a fe ff ff
  31 c0 eb a4 4c 89 ef e8 4d b3 e9 ff e9 91 fe ff ff be 0e 00 00 00 4c
  89 ef e8 5b bb e9 ff e9 e4 fe ff ff 0f 0b <0f> 0b 48 8d bd 50 ff ff ff
  89 85 40 ff ff ff e8 50 1a eb ff 8b 85

  Jan 30 17:10:02 system-box kernel: [13117.565589] RSP:
  0018:99674b78b930 EFLAGS: 00010246

  ...skipping...

  Jan 30 17:10:02 system-box kernel: [13117.565633]  ?
  ext4_mark_inode_dirty+0x1d0/0x1d0

  Jan 30 17:10:02 system-box kernel: [13117.565635]  ?
  do_writepages+0x41/0xd0

  Jan 30 17:10:02 system-box kernel: [13117.565638]  ?
  check_preempt_wakeup+0x11f/0x250

  Jan 30 17:10:02 system-box kernel: [13117.565641]
  __writeback_single_inode+0x40/0x360

  Jan 30 17:10:02 system-box kernel: [13117.565643]
  writeback_sb_inodes+0x211/0x520

  Jan 30 17:10:02 system-box kernel: [13117.565646]
  __writeback_inodes_wb+0x67/0xb0

  Jan 30 17:10:02 system-box kernel: [13117.565648]
  wb_writeback+0x25f/0x2f0

  Jan 30 17:10:02 system-box kernel: [13117.565651]  ?
  get_nr_dirty_inodes+0x46/0x70

  Jan 30 17:10:02 system-box kernel: [13117.565654]
  wb_workfn+0x32c/0x3f0

  Jan 30 17:10:02 system-box kernel: [13117.565656]  ?
  __switch_to_asm+0x34/0x70

  Jan 30 17:10:02 system-box kernel: [13117.565660]
  process_one_work+0x20f/0x3c0

  Jan 30 17:10:02 system-box kernel: [13117.565662]
  worker_thread+0x34/0x400

  Jan 30 17:10:02 system-box kernel: [13117.565664]  kthread+0x120/0x140

  Jan 30 17:10:02 system-box kernel: [13117.565667]  ?
  pwq_unbound_release_workfn+0xd0/0xd0

  Jan 30 17:10:02 system-box kernel: [13117.565668]  ?
  kthread_bind+0x40/0x40

  Jan 30 17:10:02 system-box kernel: [13117.565670]
  ret_from_fork+0x35/0x40

  Jan 30 17:10:02 system-box kernel: [13117.565671] Modules linked in:
  nf_conntrack_ipv6 nf_defrag_ipv6 vmnet(OE) parport_pc
  vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) thunderbolt rfcomm
  veth xt_nat nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter
  xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key
  xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel
  pppox msr ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat
  nf_nat_ipv4 cmac nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
  nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
  llc devlink pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE)
  ip6table_filter ip6_tables vboxdrv(OE) iptable_filter bpfilter aufs
  overlay bnep uvcvideo videobuf2_vmalloc videobuf2_memops
  videobuf2_v4l2 videobuf2_common btusb btrtl videodev btbcm

  Jan 30 17:10:02 system-box kernel: [13117.565701]  media btintel
  bluetooth ecdh_generic binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi
  snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp
  snd_hda_ext_core snd_hda_codec_realtek snd_soc_acpi
  snd_hda_codec_generic snd_soc_core snd_compress ac97_bus intel_rapl
  arc4 snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp
  snd_seq_midi coretemp snd_hda_intel snd_seq_midi_event

[Kernel-packages] [Bug 1814003] [NEW] kernel BUG at fs/ext4/inode.c:2679!

2019-01-30 Thread Moses Frost

Public bug reported:

I started seeing this bug in Ubuntu 18.04 running VMWare Workstation Pro
14. After upgrading to Ubuntu 18.10 and VMware Workstation 15 the bug
still appears. I started to ask questions on the VMware Community,
https://communities.vmware.com/thread/604705. Because I had some
additional time to troubleshoot I am also noticing that this bug is
being reported on other Linux Distributions notably:
https://bugzilla.redhat.com/show_bug.cgi?id=1662314

Conditions to reproduce. Laptop is running 2 NVMe drives with Cryptfs on
each drive (unsure if this is related). Running Vmware Workstation Pro
15 with a Windows 10 Guest upon shutting down the Windows Guest a kernel
stack strace appears in both dmesg -w and /var/log/syslog. The VM does
not gracefully stop.

Stack Trace is Below:

Jan 30 17:10:02 system-box kernel: [13117.565550] [ cut here
]

Jan 30 17:10:02 system-box kernel: [13116.565552] kernel BUG at
fs/ext4/inode.c:2679!

Jan 30 17:10:02 system-box kernel: [13117.565558] invalid opcode: 
[#1] SMP PTI

Jan 30 17:10:02 system-box kernel: [13117.565561] CPU: 0 PID: 18820
Comm: kworker/u8:0 Tainted: GW  OE 4.18.0-13-generic
#14-Ubuntu

Jan 30 17:10:02 system-box kernel: [13117.565562] Hardware name: LENOVO
20HES35Q00/20HES35Q00, BIOS N1QET79W (1.54 ) 11/16/2018

Jan 30 17:10:02 system-box kernel: [13117.565566] Workqueue: writeback
wb_workfn (flush-253:3)

Jan 30 17:10:02 system-box kernel: [13117.565569] RIP:
0010:mpage_prepare_extent_to_map+0x2bc/0x2f0

Jan 30 17:10:02 system-box kernel: [13117.565570] Code: 86 0a fe ff ff
31 c0 eb a4 4c 89 ef e8 4d b3 e9 ff e9 91 fe ff ff be 0e 00 00 00 4c 89
ef e8 5b bb e9 ff e9 e4 fe ff ff 0f 0b <0f> 0b 48 8d bd 50 ff ff ff 89
85 40 ff ff ff e8 50 1a eb ff 8b 85

Jan 30 17:10:02 system-box kernel: [13117.565589] RSP:
0018:99674b78b930 EFLAGS: 00010246

...skipping...

Jan 30 17:10:02 system-box kernel: [13117.565633]  ?
ext4_mark_inode_dirty+0x1d0/0x1d0

Jan 30 17:10:02 system-box kernel: [13117.565635]  ?
do_writepages+0x41/0xd0

Jan 30 17:10:02 system-box kernel: [13117.565638]  ?
check_preempt_wakeup+0x11f/0x250

Jan 30 17:10:02 system-box kernel: [13117.565641]
__writeback_single_inode+0x40/0x360

Jan 30 17:10:02 system-box kernel: [13117.565643]
writeback_sb_inodes+0x211/0x520

Jan 30 17:10:02 system-box kernel: [13117.565646]
__writeback_inodes_wb+0x67/0xb0

Jan 30 17:10:02 system-box kernel: [13117.565648]
wb_writeback+0x25f/0x2f0

Jan 30 17:10:02 system-box kernel: [13117.565651]  ?
get_nr_dirty_inodes+0x46/0x70

Jan 30 17:10:02 system-box kernel: [13117.565654]  wb_workfn+0x32c/0x3f0

Jan 30 17:10:02 system-box kernel: [13117.565656]  ?
__switch_to_asm+0x34/0x70

Jan 30 17:10:02 system-box kernel: [13117.565660]
process_one_work+0x20f/0x3c0

Jan 30 17:10:02 system-box kernel: [13117.565662]
worker_thread+0x34/0x400

Jan 30 17:10:02 system-box kernel: [13117.565664]  kthread+0x120/0x140

Jan 30 17:10:02 system-box kernel: [13117.565667]  ?
pwq_unbound_release_workfn+0xd0/0xd0

Jan 30 17:10:02 system-box kernel: [13117.565668]  ?
kthread_bind+0x40/0x40

Jan 30 17:10:02 system-box kernel: [13117.565670]
ret_from_fork+0x35/0x40

Jan 30 17:10:02 system-box kernel: [13117.565671] Modules linked in:
nf_conntrack_ipv6 nf_defrag_ipv6 vmnet(OE) parport_pc
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) thunderbolt rfcomm
veth xt_nat nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter
xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key
xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel
pppox msr ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat
nf_nat_ipv4 cmac nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack
nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc devlink pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE)
ip6table_filter ip6_tables vboxdrv(OE) iptable_filter bpfilter aufs
overlay bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2
videobuf2_common btusb btrtl videodev btbcm

Jan 30 17:10:02 system-box kernel: [13117.565701]  media btintel
bluetooth ecdh_generic binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi
snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp
snd_hda_ext_core snd_hda_codec_realtek snd_soc_acpi
snd_hda_codec_generic snd_soc_core snd_compress ac97_bus intel_rapl arc4
snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp snd_seq_midi
coretemp snd_hda_intel snd_seq_midi_event snd_hda_codec kvm_intel
snd_hda_core snd_hwdep snd_rawmidi kvm irqbypass snd_pcm intel_cstate
intel_rapl_perf snd_seq iwlmvm mac80211 joydev input_leds serio_raw
snd_seq_device snd_timer iwlwifi wmi_bmof intel_wmi_thunderbolt
thinkpad_acpi nvram cfg80211 ucsi_acpi snd typec_ucsi typec soundcore
intel_pch_thermal mei_me mei mac_hid acpi_pad sch_fq_codel ppdev lp
parport ip_tables x_tables autofs4 algif_skcipher af_alg

Jan 30 17:10:02 system-box kernel: [13117.565729]  dm_crypt i915 uas
nvme crct10dif_pclmul crc32_pclmul

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

2019-01-30 Thread Brad Johnson

Seeing this with a Lenovo T480.  Laptop display + USB-C dock with a
DisplayPort and HDMI out.  No issues with the HDMI connection, but the
DisplayPort connection is where I was having issues.  If the system
detected the Display Port monitor it came in as a disabled monitor.  If
I enabled it, then all screens would go blank and I would have to force
the laptop off to recover.  Currently booting back into 4.15.0-43
without 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/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:
  Confirmed

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 1813999] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

Status in linux package in Ubuntu:
Confirmed

The problem does not occur if the display is plugged in through a USBc
(non-ThunderBolt) port.

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

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

2019-01-30 Thread juliobahar

Yes I do have the same issue. using a Lenovo B50-80, started just after
the last recent update to:

Linux lenovob50-80 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

on a docking station closed lid, used to work fine now I have to keep
the lid open. and if the lid is closed the PC freezes and would have to
hard restart it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed

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 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

** Description changed:

  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/
  
- It seems that having apps open influences the bug. For example, upon a
- fresh boot I can't get this bug to work but after opening Firefox and
- closing the laptop lid it does happen.
- 
- WORKAROUND: Disable XHC1 prior to sleeping:
- > # echo XHC1 > /proc/acpi/wakeup
- 
- which has the downside of the laptop not automatically waking up after
- opening the lid, and requiring one to press the power button.
+ The first time suspending works great but after that suspending causes
+ the laptop to wake up regardless of the method used to suspend.
  
  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.

** Tags removed: kernel-bug-exists-upstream-5.0-rc2
** Tags added: kernel-bug-exists-upstream-5.0-rc4

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

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.

  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

[Kernel-packages] [Bug 1813999] [NEW] ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

2019-01-30 Thread Gene Olson

Public bug reported:

This problem appeared on the first boot Linux 4.15.0-44, and was not
present in previous kernels, including 4.15.0-43. The problem occurs
every time with 4.15.0-44. Since the problem occurred, 4.15.0-43
continues to work w/o issues.  The log should show multiple boots with
both kernels, both Xorg and Wayland.

The problem occurs wheen connecting a TB-16 dock-connected external
display, or when plugging in a TB-16 dock-connected external display
during an X session.  The symptoms are different with Xorg and Wayland,
but both cause kernel exceptions.  With Xorg the system freezes up, but
will still ping.  With Wayland the display goes black, but userland is
still accessible.  With Xorg the system is gone before the Login screen
appears.  With Wayland the login screen is okay, but the problem occurs
immediately after a successful login. The system runs normally with both
Xorg and Wayland so long as the external display is not connected.

The problem does not occur if the display is plugged in through a USBc
(non-ThunderBolt) port.

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gene   1982 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 30 16:49:20 2019
HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
InstallationDate: Installed on 2018-11-19 (72 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. XPS 15 9570
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
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/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 02MJVY
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.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.sys.vendor: Dell Inc.

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


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

** Attachment added: "syslogs.tz"
   https://bugs.launchpad.net/bugs/1813999/+attachment/5234382/+files/syslogs.tz

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

Title:
  ubuntu 18.04 linux 4.15.0-44 kernel exception with ThunderBolt display

Status in linux package in Ubuntu:
  New

Bug description:
  This problem appeared on the first boot Linux 4.15.0-44, and was not
  present in previous kernels, including 4.15.0-43. The problem occurs
  every time with 4.15.0-44. Since the problem occurred, 4.15.0-43
  continues to work w/o issues.  The log should show multiple boots with
  both kernels, both Xorg and Wayland.

  The problem occurs wheen connecting a TB-16 dock-connected external
  display, or when plugging in a TB-16 dock-connected external display
  during an X session.  The symptoms are different with Xorg and
  Wayland, but both cause kernel exceptions.  With Xorg the system
  freezes up, but will still ping.  With Wayland the display goes black,
  but userland is still accessible.  With Xorg the system is gone before
  the Login screen appears.  With Wayland the login screen is okay, but
  the problem occurs immediately after a successful login. The system
  runs normally with both Xorg and Wayland so long as the external
  display is not connected.

  The problem does not occur if the display is plugged in through a USBc
  (non-ThunderBolt) port.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1982 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 16:49:20 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (72 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb

[Kernel-packages] [Bug 1813779] Re: linux: 4.15.0-45.48 -proposed tracker

2019-01-30 Thread Brad Figg

** 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 1813780 (linux-hwe), bug 1813781 (linux-hwe-edge)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 30. January 2019 09:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
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/1813779

Title:
  linux: 4.15.0-45.48 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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 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

  backports: bug 1813780 (linux-hwe), bug 1813781 (linux-hwe-edge)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 30. January 2019 09:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1813779] Re: linux: 4.15.0-45.48 -proposed tracker

2019-01-30 Thread Steve Beattie

** Changed in: kernel-sru-workflow/security-signoff
   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/1813779

Title:
  linux: 4.15.0-45.48 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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 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

  backports: bug 1813780 (linux-hwe), bug 1813781 (linux-hwe-edge)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 30. January 2019 09:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1782205] Re: KVM SnowRidge enable new ISAs

This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu1

---
qemu (1:3.1+dfsg-2ubuntu1) disco; urgency=medium

  * Merge with Debian testing, Among many other things this fixes LP Bugs:
LP: #1806104 - fix misleading page size error on ppc64el
LP: #1782205 - SnowRidge enabled new ISAs
LP: #1786956 - upgrade to qemu >= 3.0
LP: #1809083 - Backward migration to Xenial on ppc64el
LP: #1803315 - s390x Huge page enablement
LP: #1657409 - enable virglrenderer
Remaining Changes:
- qemu-kvm to systemd unit
  - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm,
hugepages and architecture specifics
  - d/qemu-kvm.service: systemd unit to call qemu-kvm-init
  - d/qemu-system-common.install: install systemd unit and helper script
  - d/qemu-system-common.maintscript: clean old sysv and upstart scripts
  - d/qemu-system-common.qemu-kvm.default: defaults for
/etc/default/qemu-kvm
  - d/rules: install /etc/default/qemu-kvm
- Enable nesting by default
  - d/qemu-system-x86.modprobe: set nested=1 module option on intel.
(is default on amd)
  - d/qemu-system-x86.postinst: re-load kvm_intel.ko if it was loaded
without nested=1
  - d/p/ubuntu/expose-vmx_qemu64cpu.patch: expose nested kvm by default
in qemu64 cpu type.
  - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default
in qemu64 on amd
  - d/qemu-system-x86.README.Debian: document intention of nested being
default is comfort, not full support
- Distribution specific machine type (LP: 1304107 1621042 1776189 1761372)
  - d/p/ubuntu/define-ubuntu-machine-types.patch: define distro machine
types
  - d/qemu-system-x86.NEWS Info on fixed machine type defintions
for host-phys-bits=true (LP: 1776189)
  - add an info about -hpb machine type in debian/qemu-system-x86.NEWS
  - d/p/ubuntu/lp-1761372-*: provide pseries-bionic-2.11-sxxm type as
convenience with all meltdown/spectre workarounds enabled by default.
(LP: 1761372).
- improved dependencies
  - Make qemu-system-common depend on qemu-block-extra
  - Make qemu-utils depend on qemu-block-extra
  - let qemu-utils recommend sharutils
- s390x support
  - Create qemu-system-s390x package
  - Enable numa support for s390x
- arch aware kvm wrappers
- d/control: update VCS links (updated to match latest Ubuntu)
- qemu-guest-agent: freeze-hook fixes (LP: 1484990)
  - d/qemu-guest-agent.install: provide /etc/qemu/fsfreeze-hook
  - d/qemu-guest-agent.dirs: provide /etc/qemu/fsfreeze-hook.d
- d/control-in: enable RDMA support in qemu (LP: 1692476)
- enable RDMA config option
- add libibumad-dev build-dep
- tolerate ipxe size change on migrations to >=18.04 (LP: 1713490)
  - d/p/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch: old machine types
reference 256k path
  - d/control-in: depend on ipxe-qemu-256k-compat-efi-roms to be able to
handle incoming migrations from former releases.
- d/control-in: Disable capstone disassembler library support (universe)
  * Added Changes:
- d/p/ubuntu/define-ubuntu-machine-types.patch: update machine type changes
  for qemu 3.1 in the Ubuntu Disco release
- d/p/ubuntu/lp-1759509-* fix waking up VMs from dompmsuspend (LP: #1759509)
- Move s390x roms to a new qemu-system-data-s390x
  - d/qemu-system-data.install: install s390x roms as architecture:all in
qemu-system-data
  - d/rules: build s390-ccw.img with upstream Makefile
  - d/rules: build s390x-netboot.img with upstream Makefile
  - d/p/ubuntu/lp-1790901-partial-SLOF-for-s390x-netboot.patch: bring back
some SLOF bits stripped in DFSG to be able to build s390x-netboot roms
As that hack to build s390-ccw.img rom can't build s390x-netboot.img
replace it with a build-indep using the upstream makefiles.
This is less prone to miss future changes/fixes that are done to the
makefiles
  - d/control-in: add breaks/replaces for moving s390x roms from
qemu-system-s390x to qemu-system-data
- remove /dev/kvm permission handling (moved to systemd 239-6) (#892945)
  [From not yet uploaded Debian branch]
- d/p/debianize-qemu-guest-service.patch: fix path of qemu-ga
  (Closes: #918378)
- d/rules: fix qemu-kvm service for debhelper compat >=12
- d/p/ubuntu/Revert-target-i386-kvm-add-VMX-migration-blocker.patch:
  avoid misdetection of simplified nesting blocking all migrations
- d/p/ubuntu/lp-1812384-s390x-Return-specification-exception-for-
  unimplement.patch: properly return archicture defined exception
  on bad subcodes of diag 308 (LP: #1812384)
  * Dropped Changes:
- Include s390-ccw.img firmware (old style native build)
- d/rules enable install s390x-netboot.img (old style native build)
-

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2019-01-30 Thread Bug Watch Updater

Launchpad has imported 7 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=86931.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2014-10-25T20:23:14+00:00 caravena wrote:

Message with Mouse Bluetooth

[ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/4

On 2015-05-04T09:35:57+00:00 csaavedra wrote:

This is still present in 4.0.0. Bluetooth keyboard disconnects,
bluetoothd seems to crash, etc.

Do you need any further information to help debug this? This bug makes
the bluetooth keyboard unusable.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/10

On 2016-03-29T19:52:54+00:00 stephan.diestelhorst wrote:

Same in 4.2.0 (-34-generic in Ubuntu 15.10).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/14

On 2016-03-30T17:53:32+00:00 jbmacbrodie wrote:

Bluetooth behavior was good in ubuntu 15.10 - bluez5.35, blueman device
manager and kernel 4.3.6. I use a bt mouse and OEM bt keydock (Asus
T100-CHI)

Starting with 4.4 thru 4.6-rc1-next*, I have to open blueman's device
manager to search for devices after idle timeouts. I also need to leave
the device manager dialogue open/minimized to prevent rapid loss of
connection. Device pairing is remembered, but manually searching is
difficult when the pointing devices stop working. My test setup has a
usb mouse as a workaround.

dmesg has "unknown main item tag 0x0" after each idle timeout". If I
move mouse during boot, it will auto-connect, but it then suffers a
rapid timeout soon after booting. See dmesg posted at #114561. It
looks like something is incrementing the bluetooth input assignment #
when anything times out.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/15

On 2018-01-12T09:21:14+00:00 robsmith11 wrote:

Has anyone solved this yet??

I have the same issue with a bluetooth keyboard and kernel 4.14.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/29

On 2018-01-12T17:26:47+00:00 jbmacbrodie wrote:

The issue was fixed for the Asus T100 (baytrail) 2-in-1 family. See this
commit.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=c4c285da1ee18582ace366f07e56e355c20ebc49
which is in kernel 4.15.

You could try adding the quirk for your device.

(No kernel maintainer has acknowledged this bug report.)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/30

On 2019-01-30T18:27:54+00:00 mybigspam wrote:

It's not clear from the description what is the problem exactly?
I have similar symptoms with "unknown main item tag 0x0" message after timeout.

But my problem is that bluetooth keyboard disconnects on timeout (which
is normal), but then, on the first key press it's just loss, while the
keyboard reconnects successfully.

It doesn't occurs on the same system with Windows 10 - the key doesn't
lost on reconnect.

I wonder if it can be the same problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113/comments/35

** Changed in: linux
Status: Unknown => Confirmed

** Changed in: linux
Importance: Unknown => Medium

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

Title:
hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
Message with Mouse Bluetooth

[ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
0x0

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-23-generic 3.16.0-23.31
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: caravena 3344 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Oct 24 05:22:54 2014
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on

[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2019-01-30 Thread antubis

I also want to confirm that the sound has come back when I upgraded the
kernel to 4.19.18. I am using Mint 19.1 and by default it didn't work.

Warning! I first upgraded to 4.20.5 but it didn't work. I switched to
the 4.19 and it magically started to work!

And on a side note it works better than the stock windows version. The
sound card was making weird static noises when used on Windows 10.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+subscriptions

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

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

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

apport-collect 1813847

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

Title:
  af-alg stressor triggers modprobe throttling

Status in Stress-ng:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Due to the combination of high core counts and perhaps a lack of
  available hash/crypto hardware acceleration drivers, arm64 server
  platforms generate a lot of noisy modprobe throttling messages when
  running the af-alg stressor. This appears to be partially mitigated in
  master by disabling hashes/ciphers once they are found to be not
  present. But, w/ 96 cores/hogs, we presumably still hit the kernel
  with 96 * (nr_hashes + nr_ciphers) before that mitigation takes
  effect, and that is sufficient to cause the kernel to emit throttling
  messages.

  
  $ sudo dmesg -c > /dev/null ; ./stress-ng --af-alg 0 --af-alg-ops=20; 
sudo dmesg -c
  stress-ng: info:  [76141] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
  stress-ng: info:  [76141] dispatching hogs: 96 af-alg
  stress-ng: info:  [76141] successful run completed in 0.40s
  [ 5808.489046] __request_module: 25 callbacks suppressed
  [ 5808.489050] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489503] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489724] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489731] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490092] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-xor-all, throttling...
  [ 5808.490235] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash-all, throttling...
  [ 5808.490308] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490367] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490597] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813847/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  ETPS/2 Elantech TrackPoint is locked vertically / can not move pointer
  right and left

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a Lenovo Thinkpad T480s with Ubuntu Mate 18.04. On the
  fresh setup the trackpoint worked flawlessly. After some kernel
  updates (current one is 4.15.0-44) the trackpoint got
  "stucked"/"locked" vertically. That means I can only move the pointer
  up and down and not right and left. Sometimes I can move the pointer
  to the right but then it jumps around uncontrollably and gets locked
  at the right end of the desktop.

  I tried a lot of different things: Compiled newest libinput, tried
  hwe-kernel 4.18 and mainline-kernel 4.20. None of these made it work.
  On random occassions the trackpoint worked fine but got stucked once
  again in the same session. I think it got stucked when I
  simultaneously moved the trackpoint and touched the touchpad with my
  palm.

  Touchpad is working fine though!

  $ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech TrackPoint  id=12   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=10   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=13   [slave  
keyboard (3)]

  $ dmesg | grep -i elan
  [2.930410] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x7f3001)
  [2.940877] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x0f.
  [2.951284] psmouse serio1: elantech: Elan sample query result 00, 20, c9
  [2.994917] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input7
  [3.008529] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

  Is this a driver issue with elantech driver because the T480s is new 
hardware? I stumpled upon different patches from Benjamin Tissoires who 
suggests something like that:
  https://patchwork.kernel.org/patch/10638703/
  https://patchwork.kernel.org/patch/10324641/

  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: 1974 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Jan 30 21:59:58 2019
  HibernationDevice: RESUME=UUID=0f5f9333-5826-4e4b-ba22-a0a7fce65754
  InstallationDate: Installed on 2018-07-27 (187 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:2113 Acer, Inc
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20L8S02D00
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic 
root=UUID=a69059e4-d10d-471b-a8a9-88692ccbabdd 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: 04/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET35W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET35W(1.12):bd04/09/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family:

[Kernel-packages] [Bug 1813988] [NEW] ETPS/2 Elantech TrackPoint is locked vertically / can not move pointer right and left

2019-01-30 Thread arvid

Public bug reported:

I am using a Lenovo Thinkpad T480s with Ubuntu Mate 18.04. On the fresh
setup the trackpoint worked flawlessly. After some kernel updates
(current one is 4.15.0-44) the trackpoint got "stucked"/"locked"
vertically. That means I can only move the pointer up and down and not
right and left. Sometimes I can move the pointer to the right but then
it jumps around uncontrollably and gets locked at the right end of the
desktop.

I tried a lot of different things: Compiled newest libinput, tried hwe-
kernel 4.18 and mainline-kernel 4.20. None of these made it work. On
random occassions the trackpoint worked fine but got stucked once again
in the same session. I think it got stucked when I simultaneously moved
the trackpoint and touched the touchpad with my palm.

Touchpad is working fine though!

$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad  id=11   [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech TrackPointid=12   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Sleep Button  id=8[slave  keyboard (3)]
↳ Integrated Camera: Integrated C   id=9[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=10   [slave  keyboard (3)]
↳ ThinkPad Extra Buttonsid=13   [slave  keyboard (3)]

$ dmesg | grep -i elan
[2.930410] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x7f3001)
[2.940877] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x0f.
[2.951284] psmouse serio1: elantech: Elan sample query result 00, 20, c9
[2.994917] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input7
[3.008529] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

Is this a driver issue with elantech driver because the T480s is new hardware? 
I stumpled upon different patches from Benjamin Tissoires who suggests 
something like that:
https://patchwork.kernel.org/patch/10638703/
https://patchwork.kernel.org/patch/10324641/

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: 1974 F pulseaudio
CurrentDesktop: MATE
Date: Wed Jan 30 21:59:58 2019
HibernationDevice: RESUME=UUID=0f5f9333-5826-4e4b-ba22-a0a7fce65754
InstallationDate: Installed on 2018-07-27 (187 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:2113 Acer, Inc
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20L8S02D00
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic 
root=UUID=a69059e4-d10d-471b-a8a9-88692ccbabdd 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: 04/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET35W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET35W(1.12):bd04/09/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic elantech trackpoint

** Description changed:

  I am using a Lenovo Thinkpad T480s with Ubuntu Mate 18.04. On the fresh
  setup the trackpoint worked flawlessly. After some kernel updates
  (current one is 4.15.0-44) the trackpoint got "stucked"/"locked"
  vertically. That means I can only move the pointer up and down and not
  right and left. Sometimes I can move the pointer to the right but then
  it jumps around

[Kernel-packages] [Bug 1813847] Re: af-alg stressor triggers modprobe throttling

2019-01-30 Thread dann frazier

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

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

Title:
  af-alg stressor triggers modprobe throttling

Status in Stress-ng:
  In Progress
Status in linux package in Ubuntu:
  New

Bug description:
  Due to the combination of high core counts and perhaps a lack of
  available hash/crypto hardware acceleration drivers, arm64 server
  platforms generate a lot of noisy modprobe throttling messages when
  running the af-alg stressor. This appears to be partially mitigated in
  master by disabling hashes/ciphers once they are found to be not
  present. But, w/ 96 cores/hogs, we presumably still hit the kernel
  with 96 * (nr_hashes + nr_ciphers) before that mitigation takes
  effect, and that is sufficient to cause the kernel to emit throttling
  messages.

  
  $ sudo dmesg -c > /dev/null ; ./stress-ng --af-alg 0 --af-alg-ops=20; 
sudo dmesg -c
  stress-ng: info:  [76141] defaulting to a 86400 second (1 day, 0.00 secs) run 
per stressor
  stress-ng: info:  [76141] dispatching hogs: 96 af-alg
  stress-ng: info:  [76141] successful run completed in 0.40s
  [ 5808.489046] __request_module: 25 callbacks suppressed
  [ 5808.489050] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489503] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489724] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.489731] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490092] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-xor-all, throttling...
  [ 5808.490235] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash-all, throttling...
  [ 5808.490308] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490367] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...
  [ 5808.490597] request_module: kmod_concurrent_max (0) close to 0 
(max_modprobes: 50), for module crypto-ghash, throttling...

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1813847/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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-30 Thread Will Carroll

Confirmed same issue on Thinkpad T480 with docking station. One external
monitor over HDMI 1440p @ 60Hz. Issue also occurs occasionally upon
resuming from suspend with no external monitors attached. Occurs every
time with monitor attached on boot, resume, screen lock, or display
sleep.

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

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 1813984] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  Nvidia Module does not load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Nvidia module does not load in the last kernel 4.15.0-44-generic . If
  I load the previous kernel it works without problem. I use GRUB.

  Kernel Log:

  Jan 29 12:54:34 jbg kernel: [7.374623] nvidia: loading out-of-tree module 
taints kernel.
  Jan 29 12:54:34 jbg kernel: [7.374632] nvidia: module license 'NVIDIA' 
taints kernel.
  Jan 29 12:54:34 jbg kernel: [7.374633] Disabling lock debugging due to 
kernel taint
  Jan 29 12:54:34 jbg kernel: [7.380512] nvidia: module verification 
failed: signature and/or required key missing - tainting kernel

  
  Thank you for your work!


  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/controlC1:  gdm1214 F pulseaudio
    jbg1911 F pulseaudio
   /dev/snd/controlC0:  gdm1214 F pulseaudio
    jbg1911 F pulseaudio
  Date: Wed Jan 30 21:19:29 2019
  InstallationDate: Installed on 2018-10-04 (118 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=bfed3b0e-db36-4939-b9a0-d5d24baff2f6 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-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.64
  dmi.board.name: 176B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.1F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.64:bd10/07/2016:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570w
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~kernel-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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-core.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234358/+files/dmesg-core.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-processors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234362/+files/dmesg-processors.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

Alright went through all steps! For the suspend command I replaced `pm-
suspend` with `systemctl suspend`, since I don't have the first,
hopefully the latter is okay too.

For the "usbcore.dyndbg=+p" step I was not sure how, I modified grub
with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.dyndbg=+p" and ran
grub update, output in attached "dmesg-2-usbcore-dyndbg.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-devices.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234359/+files/dmesg-devices.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-none.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234361/+files/dmesg-none.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

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

[Kernel-packages] [Bug 1813779] Re: linux: 4.15.0-45.48 -proposed tracker

2019-01-30 Thread Steve Beattie

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

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

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

Title:
  linux: 4.15.0-45.48 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
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 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

  backports: bug 1813780 (linux-hwe), bug 1813781 (linux-hwe-edge)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 30. January 2019 09:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
verification-testing: Ongoing -- testing in progress

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-2-usbcore-dyndbg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234357/+files/dmesg-2-usbcore-dyndbg.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

** Attachment added: "dmesg-freezer.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234360/+files/dmesg-freezer.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

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

[Kernel-packages] [Bug 1813902] Re: Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

I'm having the same issue on a Dell Latitude 5289 laptop connected to a
dell USB-C dock with 2 external monitors, and USB keyboard and mouse
(Razer Naga Chroma).

My computer will immediately lock up upon pressing Super + L to lock the
screen when it's connected to the dock. When disconnected from the dock,
it wakes up fine.

This is isolated to 4.15.0-44 for me as well. I am unable to replicate
in 4.15.0-43.

Related issues:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813956
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1813902

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

Title:
  Lenovo Thinkpad T540p - Kernel Crash 4.15.0-44 (18.04 LTS)

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  When notebook is in docking station the kernel crashes after bootup and logon 
in GDM.
  If notebook is in standalone mode without any external devices connected 
everything works.

  Tried to step back to Kernel 4.15.0-43-generic and everything works
  like a charm.

  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:
Installed: 4.15.0-44.47
Candidate: 4.15.0-44.47
Version table:
   *** 4.15.0-44.47 500
  500 http://at.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

  
  /var/log/syslog reports a Kernel BUG...
  Jan 30 10:18:41 bexlt036 kernel: [   34.993161] BUG: unable to handle kernel 
NULL pointer dereference at 0245
  Jan 30 10:18:41 bexlt036 kernel: [   34.993215] IP: 
intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993217] PGD 0 P4D 0 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993222] Oops:  [#1] SMP PTI
  Jan 30 10:18:41 bexlt036 kernel: [   34.993225] Modules linked in: ccm 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep btusb 
btrtl btbcm cdc_mbim btintel cdc_wdm bluetooth cdc_ncm usbnet uvcvideo cdc_acm 
mii ecdh_generic joydev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek 
snd_hda_codec_generic irqbypass snd_hda_intel intel_cstate snd_hda_codec 
intel_rapl_perf snd_hda_core snd_hwdep thinkpad_acpi snd_pcm nvram rmi_smbus 
iwlmvm rmi_core input_leds videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
mac80211 snd_seq_midi
  Jan 30 10:18:41 bexlt036 kernel: [   34.993282]  videobuf2_core serio_raw 
videodev snd_seq_midi_event media iwlwifi snd_rawmidi wmi_bmof snd_seq 
rtsx_pci_ms memstick snd_seq_device cfg80211 snd_timer snd mei_me soundcore mei 
mac_hid lpc_ich shpchp ie31200_edac sch_fq_codel sunrpc parport_pc ppdev lp 
parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt 
hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i915 ahci aesni_intel 
i2c_algo_bit e1000e aes_x86_64 drm_kms_helper crypto_simd glue_helper cryptd 
psmouse syscopyarea libahci sysfillrect sysimgblt fb_sys_fops drm ptp i2c_i801 
rtsx_pci pps_core wmi video
  Jan 30 10:18:41 bexlt036 kernel: [   34.993339] CPU: 2 PID: 2890 Comm: Xorg 
Not tainted 4.15.0-44-generic #47-Ubuntu
  Jan 30 10:18:41 bexlt036 kernel: [   34.993341] Hardware name: LENOVO 
20BE00B5GE/20BE00B5GE, BIOS GMET66WW (2.14 ) 07/01/2014
  Jan 30 10:18:41 bexlt036 kernel: [   34.993375] RIP: 
0010:intel_ddi_post_disable+0x54/0x170 [i915]
  Jan 30 10:18:41 bexlt036 kernel: [   34.993377] RSP: 0018:a739c28ef9f0 
EFLAGS: 00010297
  Jan 30 10:18:41 bexlt036 kernel: [   34.993380] RAX: 0007 RBX: 
95550026e000 RCX: c054f272
  Jan 30 10:18:41 bexlt036 kernel: [   34.993383] RDX:  RSI: 
 RDI: 95550026e000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993385] RBP: a739c28efa20 R08: 
 R09: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993387] R10: 0047 R11: 
028f R12: 
  Jan 30 10:18:41 bexlt036 kernel: [   34.993390] R13: 95550026e000 R14: 
9554ffef8000 R15: 9554ffa62000
  Jan 30 10:18:41 bexlt036 kernel: [   34.993393] FS:  7fbfc6b5b600() 
GS:95551e28() knlGS:
  Jan 30 10:18:41 bexlt036 kernel: [   34.993395] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 30 10:18:41 bexlt036 kernel: [   34.993398] CR2: 0245 CR3: 
0003bc132003 CR4:

[Kernel-packages] [Bug 1813956] Re: Lenovo T480: problem with external screens

Related issues:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813956
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1813902

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

Title:
  Lenovo T480: problem with external screens

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup: two external screens connected through separate DP ports and a
  docking station to a laptop Lenovo T480

  When the laptop is launched in the docking station (lid is closed) the 
screens remain off (there is information about missing signal).
  When the laptop is launched out of docking station (using only the internal 
screen), after logging to the Gnome session, connecting to the docking station: 
there is an image on two external screens. However, once the laptop is 
suspended or screensaver enabled (switch off all screens), after wakeup, all 
screens remain off.

  This bug is 4.15.0-44 kernel specific. With the previous version
  4.15.0-43 the external screens were served properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:27:50 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

2019-01-30 Thread Magnus Breder Birkenes

@MaskedDriver: Does blacklisting the mei_me module (Intel Management
Engine) fix the issue? That fixed the problem some weeks ago, perhaps
the bug has re-appeared. I have not upgraded to .44 yet...

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1813984] [NEW] Nvidia Module does not load

2019-01-30 Thread Jorge

Public bug reported:

Nvidia module does not load in the last kernel 4.15.0-44-generic . If I
load the previous kernel it works without problem. I use GRUB.

Kernel Log:

Jan 29 12:54:34 jbg kernel: [7.374623] nvidia: loading out-of-tree module 
taints kernel.
Jan 29 12:54:34 jbg kernel: [7.374632] nvidia: module license 'NVIDIA' 
taints kernel.
Jan 29 12:54:34 jbg kernel: [7.374633] Disabling lock debugging due to 
kernel taint
Jan 29 12:54:34 jbg kernel: [7.380512] nvidia: module verification failed: 
signature and/or required key missing - tainting kernel


Thank you for your work!


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/controlC1:  gdm1214 F pulseaudio
  jbg1911 F pulseaudio
 /dev/snd/controlC0:  gdm1214 F pulseaudio
  jbg1911 F pulseaudio
Date: Wed Jan 30 21:19:29 2019
InstallationDate: Installed on 2018-10-04 (118 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Hewlett-Packard HP EliteBook 8570w
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=bfed3b0e-db36-4939-b9a0-d5d24baff2f6 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-44-generic N/A
 linux-backports-modules-4.15.0-44-generic  N/A
 linux-firmware 1.173.3
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IAV Ver. F.64
dmi.board.name: 176B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 50.1F
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.64:bd10/07/2016:svnHewlett-Packard:pnHPEliteBook8570w:pvrA1029D1102:rvnHewlett-Packard:rn176B:rvrKBCVersion50.1F:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8570w
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic

** Description changed:

- Nvidia module does not load in the last kernel.
+ Nvidia module does not load in the last kernel 4.15.0-44-generic . If I
+ load the previous kernel it works without problem. I use GRUB.
  
  Kernel Log:
  
  Jan 29 12:54:34 jbg kernel: [7.374623] nvidia: loading out-of-tree module 
taints kernel.
  Jan 29 12:54:34 jbg kernel: [7.374632] nvidia: module license 'NVIDIA' 
taints kernel.
  Jan 29 12:54:34 jbg kernel: [7.374633] Disabling lock debugging due to 
kernel taint
  Jan 29 12:54:34 jbg kernel: [7.380512] nvidia: module verification 
failed: signature and/or required key missing - tainting kernel
  
+ 
  Thank you for your work!
+ 
  
  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/controlC1:  gdm1214 F pulseaudio
-   jbg1911 F pulseaudio
-  /dev/snd/controlC0:  gdm1214 F pulseaudio
-   jbg1911 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  gdm1214 F pulseaudio
+   jbg1911 F pulseaudio
+  /dev/snd/controlC0:  gdm1214 F pulseaudio
+   jbg1911 F pulseaudio
  Date: Wed Jan 30 21:19:29 2019
  InstallationDate: Installed on 2018-10-04 (118 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP EliteBook 8570w
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=bfed3b0e-db36-4939-b9a0-d5d24baff2f6 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.
+  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:
-

[Kernel-packages] [Bug 1813956] Re: Lenovo T480: problem with external screens

I'm having the same issue on a Dell Latitude 5289 laptop connected to a
dell USB-C dock with 2 external monitors, and USB keyboard and mouse
(Razer Naga Chroma).

My computer will immediately lock up upon pressing Super + L to lock the
screen when it's connected to the dock. When disconnected from the dock,
it wakes up fine.

This is isolated to 4.15.0-44 for me as well. I am unable to replicate
in 4.15.0-43.

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

Title:
  Lenovo T480: problem with external screens

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setup: two external screens connected through separate DP ports and a
  docking station to a laptop Lenovo T480

  When the laptop is launched in the docking station (lid is closed) the 
screens remain off (there is information about missing signal).
  When the laptop is launched out of docking station (using only the internal 
screen), after logging to the Gnome session, connecting to the docking station: 
there is an image on two external screens. However, once the laptop is 
suspended or screensaver enabled (switch off all screens), after wakeup, all 
screens remain off.

  This bug is 4.15.0-44 kernel specific. With the previous version
  4.15.0-43 the external screens were served properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:27:50 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

I'm having the same issues today after upgrading to 4.15.0.44-generic on
a Dell Latitude 5289 Ubuntu 18.04.1

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

Thank you for your replies Christopher & Kai-Heng, sorry for the slow
reply I'm trying to find time to debug and figure out how to debug.

Disabling XHC1 does not seem to solve this anymore, I guess one of the updates 
last week changed the behavior. Both with XHC1 enabled and disabled I get the 
following:
1) Suspending with `systemctl suspend`, closing the laptop lid or using the 
power button for the first time works perfectly.
2) Waking up by pressing a key or pressing the power button.
3) Suspending a 2nd time with...
  4a) lid open: Laptop seems to suspend but wakes up immediately to the login 
screen.
  4b) lid closed: Laptop seems to go in a loop, I can see the light flashing 
multiple times, things go haywire, after opening the lid there is a black 
screen with blinking cursor, can't type anything.

Attached is the dmesg output, maybe interesting info on line 1284 where
it states usb2 failed to suspend.

I'll try to add more information with pm_trace.

** Attachment added: "dmesg-2-systemctl-suspend-keywake.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+attachment/5234340/+files/dmesg-2-systemctl-suspend-keywake.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/1812561

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

Status in linux package in Ubuntu:
  Incomplete

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

  It seems that having apps open influences the bug. For example, upon a
  fresh boot I can't get this bug to work but after opening Firefox and
  closing the laptop lid it does happen.

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

  which has the downside of the laptop not automatically waking up after
  opening the lid, and requiring one to press the power button.

  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.

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

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

[Kernel-packages] [Bug 1813831] Re: Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

2019-01-30 Thread Besmir Zanaj

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

note towards the end of the log file

root@bzanaj2019:~# journalctl -k -b -1
...
Jan 30 14:23:52 bzanaj2019 kernel: BUG: unable to handle kernel NULL pointer 
dereference at 0245
Jan 30 14:23:52 bzanaj2019 kernel: IP: intel_ddi_post_disable+0x54/0x170 [i915]
Jan 30 14:23:52 bzanaj2019 kernel: PGD 0 P4D 0 
Jan 30 14:23:52 bzanaj2019 kernel: Oops:  [#1] SMP PTI
Jan 30 14:23:52 bzanaj2019 kernel: Modules linked in: hid_generic usbhid hid 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_
Jan 30 14:23:52 bzanaj2019 kernel:  sparse_keymap joydev cfg80211 serio_raw 
snd_soc_sst_ipc rtsx_pci_ms snd_soc_acpi snd_hda_codec_realtek 
snd_hda_codec_generic 
Jan 30 14:23:52 bzanaj2019 kernel:  fb_sys_fops crypto_simd glue_helper e1000e 
cryptd psmouse drm ahci ptp libahci pps_core i2c_i801 rtsx_pci wmi video
Jan 30 14:23:52 bzanaj2019 kernel: CPU: 2 PID: 10225 Comm: kworker/2:2 Tainted: 
G   OE4.15.0-44-generic #47-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/1813831

Title:
  Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 LTS on a HP EliteBook 840 G5 with docking station 
and two screens attached via DisplayPort.
  Reproducibly, when I close the lid of my notebook, the kernel 
4.15.0-44.47-generic crashes with a Oops in i915 / intel_ddi_post_disable.
  The previous kernel 4.15.0-43.46-generic works without problems.

  Oops:

  [  224.498572] BUG: unable to handle kernel NULL pointer dereference at 
0245
  [  224.498658] IP: intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498663] PGD 0 P4D 0 
  [  224.498672] Oops:  [#1] SMP PTI
  [  224.498677] Modules linked in: hid_logitech_hidpp hid_logitech_dj 
hid_cherry usbhid rfcomm nfnetlink xfrm_user xfrm_algo xt_addrtype overlay aufs 
wireguard(OE) ip6_udp_tunnel udp_tunnel thunderbolt ccm xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
ipt_REJECT nf_reject_ipv4 xt_tcpudp devlink ebtable_filter ebtables bnep 
nls_iso8859_1 hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_hda_codec_conexant snd_hda_codec_generic 
snd_pcm_dmaengine arc4 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi iwlmvm mac80211 intel_rapl
  [  224.498761]  x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi 
kvm_intel snd_seq kvm irqbypass intel_cstate hp_wmi intel_rapl_perf cfg80211 
sparse_keymap intel_wmi_thunderbolt joydev input_leds snd_seq_device serio_raw 
wmi_bmof snd_timer snd soundcore uvcvideo videobuf2_vmalloc btusb 
videobuf2_memops btrtl videobuf2_v4l2 btbcm videobuf2_core btintel videodev 
media bluetooth ecdh_generic shpchp mei_me mei ucsi_acpi typec_ucsi idma64 
typec virt_dma intel_lpss_pci processor_thermal_device intel_pch_thermal 
intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone mac_hid 
int3400_thermal acpi_pad acpi_thermal_rel hp_wireless sch_fq_codel 
iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc 
arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher
  [  224.498851]  af_alg dm_crypt crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel i915 aes_x86_64 crypto_simd glue_helper 
cryptd e1000e ptp i2c_algo_bit pps_core drm_kms_helper psmouse syscopyarea 
sysfillrect sysimgblt fb_sys_fops nvme nvme_core drm i2c_i801 i2c_hid wmi hid 
video pinctrl_sunrisepoint
  [  224.498895] CPU: 0 PID: 1952 Comm: Xorg Tainted: G   OE
4.15.0-44-generic #47-Ubuntu
  [  224.498899] Hardware name: HP HP EliteBook 840 G5/83B2, BIOS Q78 Ver. 
01.04.00 09/12/2018
  [  224.498961] RIP: 0010:intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498966] RSP: 0018:bf5cc45ab9f0 EFLAGS: 00010297
  [  224.498971] RAX: 0007 RBX: 9803af6ff000 RCX: 
c0744272
  [  224.498974] RDX:  RSI:  RDI: 
9803af6ff000
  [  224.498978] RBP: bf5cc45aba20 R08: 0003 R09: 

  [  224.498982] R10: 0209 R11: 0170 R12: 

  [  224.498985] R13: 9803af6ff000 R14: 9803aed9 R15: 
98031202d000
  [  224.498991] FS:  7ff14e363600() GS:9803df40() 
knlGS:
  [  224.498995] CS:  0010 DS:  ES:  CR0: 80050033
  [  224.498999] CR2: 0245 CR3: 000830496006 CR4: 
003606f0
  [  224.499002] Call Trace:
  [  224.499064]  ? intel_dp_sink_dpms+0xbb/0xf0

[Kernel-packages] [Bug 1813831] Re: Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

2019-01-30 Thread Besmir Zanaj

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

same issue here when disconnecting from Dell E-Port Replicator PR02X
Docking Station

** Attachment added: "Freeze after update from 4.15.0.43 to 4.15.0.44"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813831/+attachment/5234339/+files/1813831.log

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

Title:
  Oops: NULL pointer dereference intel_ddi_post_disable+0x54/0x170

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 18.04 LTS on a HP EliteBook 840 G5 with docking station 
and two screens attached via DisplayPort.
  Reproducibly, when I close the lid of my notebook, the kernel 
4.15.0-44.47-generic crashes with a Oops in i915 / intel_ddi_post_disable.
  The previous kernel 4.15.0-43.46-generic works without problems.

  Oops:

  [  224.498572] BUG: unable to handle kernel NULL pointer dereference at 
0245
  [  224.498658] IP: intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498663] PGD 0 P4D 0 
  [  224.498672] Oops:  [#1] SMP PTI
  [  224.498677] Modules linked in: hid_logitech_hidpp hid_logitech_dj 
hid_cherry usbhid rfcomm nfnetlink xfrm_user xfrm_algo xt_addrtype overlay aufs 
wireguard(OE) ip6_udp_tunnel udp_tunnel thunderbolt ccm xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c 
ipt_REJECT nf_reject_ipv4 xt_tcpudp devlink ebtable_filter ebtables bnep 
nls_iso8859_1 hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_hda_codec_hdmi snd_soc_core 
snd_compress ac97_bus snd_hda_codec_conexant snd_hda_codec_generic 
snd_pcm_dmaengine arc4 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi iwlmvm mac80211 intel_rapl
  [  224.498761]  x86_pkg_temp_thermal intel_powerclamp coretemp iwlwifi 
kvm_intel snd_seq kvm irqbypass intel_cstate hp_wmi intel_rapl_perf cfg80211 
sparse_keymap intel_wmi_thunderbolt joydev input_leds snd_seq_device serio_raw 
wmi_bmof snd_timer snd soundcore uvcvideo videobuf2_vmalloc btusb 
videobuf2_memops btrtl videobuf2_v4l2 btbcm videobuf2_core btintel videodev 
media bluetooth ecdh_generic shpchp mei_me mei ucsi_acpi typec_ucsi idma64 
typec virt_dma intel_lpss_pci processor_thermal_device intel_pch_thermal 
intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone mac_hid 
int3400_thermal acpi_pad acpi_thermal_rel hp_wireless sch_fq_codel 
iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc 
arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher
  [  224.498851]  af_alg dm_crypt crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel i915 aes_x86_64 crypto_simd glue_helper 
cryptd e1000e ptp i2c_algo_bit pps_core drm_kms_helper psmouse syscopyarea 
sysfillrect sysimgblt fb_sys_fops nvme nvme_core drm i2c_i801 i2c_hid wmi hid 
video pinctrl_sunrisepoint
  [  224.498895] CPU: 0 PID: 1952 Comm: Xorg Tainted: G   OE
4.15.0-44-generic #47-Ubuntu
  [  224.498899] Hardware name: HP HP EliteBook 840 G5/83B2, BIOS Q78 Ver. 
01.04.00 09/12/2018
  [  224.498961] RIP: 0010:intel_ddi_post_disable+0x54/0x170 [i915]
  [  224.498966] RSP: 0018:bf5cc45ab9f0 EFLAGS: 00010297
  [  224.498971] RAX: 0007 RBX: 9803af6ff000 RCX: 
c0744272
  [  224.498974] RDX:  RSI:  RDI: 
9803af6ff000
  [  224.498978] RBP: bf5cc45aba20 R08: 0003 R09: 

  [  224.498982] R10: 0209 R11: 0170 R12: 

  [  224.498985] R13: 9803af6ff000 R14: 9803aed9 R15: 
98031202d000
  [  224.498991] FS:  7ff14e363600() GS:9803df40() 
knlGS:
  [  224.498995] CS:  0010 DS:  ES:  CR0: 80050033
  [  224.498999] CR2: 0245 CR3: 000830496006 CR4: 
003606f0
  [  224.499002] Call Trace:
  [  224.499064]  ? intel_dp_sink_dpms+0xbb/0xf0 [i915]
  [  224.499118]  intel_mst_post_disable_dp+0x99/0xd0 [i915]
  [  224.499175]  intel_encoders_post_disable.isra.102+0x66/0x80 [i915]
  [  224.499226]  haswell_crtc_disable+0xe8/0x150 [i915]
  [  224.499280]  intel_atomic_commit_tail+0x7ea/0xd30 [i915]
  [  224.499330]  intel_atomic_commit+0x277/0x2b0 [i915]
  [  224.499367]  drm_atomic_commit+0x51/0x60 [drm]
  [  224.499387]  drm_atomic_helper_set_config+0x7c/0x90 [drm_kms_helper]
  [  224.499414]  __drm_mode_set_config_internal+0x6b/0x120 [drm]
  [  224.499440]  drm_mode_setcrtc+0x47f/0x660 [drm]
  [  224.499464]  ? drm_mode_getcrtc+0x190/0x190 [drm]
  [  224.499486]  drm_ioctl_kernel+0x5f/0xb0 [drm]
  [  224.499507]  drm_ioctl+0x31b/0x3d0 [drm]
  [  224.499528]

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

2019-01-30 Thread Thomas DEBESSE

@paed808 see my comment on that thread, as a dmesg from the faulty
kernel would be useful to compare. By the way I would be surprised the
bugs are the same because you really use a very far more recent hardware
(mine is perhaps four years older than yours), but if the bug is in a
shared component it's possible.

Note that I'm able to run a 4.20 kernel from liquorix (was the easiest
way for me to try out a newer kernel at this point, but I may try an
official ubuntu kernel from kernel ppa instead) so it looks like the bug
I face is fixed upstream. May be good to backport on official current
kernel.

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

Title:
  [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After updated an old laptop to Ubuntu Cosmic (was running Xenial
  before) the graphic hangs at startup, nothing is displayed but a grey
  screen (grub residual), note that the recovery boot option using
  `nodmodeset` displays a text console and I'm still able to log-in over
  a serial tty on normal boot so kernel is alive but computer is not
  usable due to lack graphic support.

  Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase
  - http://www.thinkwiki.org/wiki/Category:X61_Tablet
  - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase
  GPU is an Intel GMA X3100
  - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100

  Some information:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.10
  Release:  18.10
  Codename: cosmic

  # uname -a
  Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # lspci -vvv -nn -s 00:02.0
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  8b 52 
08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 
  [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287
  [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: 
c27190303044
  [2.709180] RDX:  RSI: 01a8 RDI: 
0150
  [2.709180] RBP: c2718067b988 R08: 0001 R09: 
0002
  [2.709180] R10: 0001 R11: 9e5533e87200 R12: 
0202
  [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 
9e5533ab8000
  [2.709180] FS:  7fd9f63c88c0() GS:9e557e40() 
knlGS:
  [2.709180] CS:  0010 DS:  ES:  CR0: 80050033
  [2.709180] CR2: 0008 CR3: 34302000 CR4: 
06f0
  [2.709180] Call Trace:
  [2.709180]  i915_request_alloc+0x24e/0x370 [i915]
  [2.709180]  i915_gem_init+0x26b/0x470 [i915]
  [2.709180]  i915_driver_load+0xab8/0xd80 [i915]
  [2.709180]  ? mutex_lock+0x12/0x30
  [2.709180]  i915_pci_probe+0x46/0x60 [i915]
  [2.709180]  local_pci_probe+0x46/0x90
  [2.709180]  pci_device_probe+0x11c/0x1a0
  [2.709180]  driver_probe_device+0x2e3/0x460
  [2.709180]  __driver_attach+0xe4/0x110
  [2.709180]  ? driver_probe_device+0x460/0x460
  [2.709180]  bus_for_each_dev+0x74/0xb0
  [2.709180]  ? kmem_cache_alloc_trace+0x1c4/0x1d0
  [2.709180]  driver_attach+0x1e/0x20
  [2.709180]  bus_add_driver+0x159/0x230
  [2.709180]  ? 0xc0474000
  [2.709180]  driver_register+0x70/0xc0
  [2.709180]  ? 0xc0474000
  [2.709180]  __pci_register_driver+0x57/0x60
  [2.709180]  i915_init+0x55/0x58 [i915]
  [2.709180]  do_one_initcall+0x4a/0x1c4
  [2.709180]  ? _cond_resched+0x19/0x30
  [2.709180]  ? kmem_cache_alloc_trace+0xb8/0x1d0
  [2.709180]  ? do_init_module+0x27/0x220
  [2.709180]  do_init_module+0x60/0x220
  [2.709180]  load_module+0x14f4/0x1890
  [2.709180]  __do_sys_finit_module+0xbd/0x120
  [2.709180]  ? __do_sys_finit_module+0xbd/0x120
  [2.709180]  __x64_sys_finit_module+0x1a/0x20
  [2.709180]  do_syscall_64+0x5a/0x110
  [2.709180]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.709180] RIP: 0033:0x7fd9f6e4d219
  [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 
  [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 
0139
  [2.709180] RAX: ffda RBX:

[Kernel-packages] [Bug 1813657] Re: 4.18.0-14 doesn't boot past grub

2019-01-30 Thread Thomas DEBESSE

Can you provide a new dmesg output from 4.18 kernel since you discovered
you are able to boot on recovery mode? Just dump it somewhere so you can
recover it once booted graphically with another kernel.

Basically once you are in front of the recovery screen, select the
option to enable network, not because of network but because it's known
to also mount filesystems in write mode, then select the option to open
a root console, then type that:

dmesg > /var/log/dmesg.$(uname -r)

It will produce a file named like /var/log/dmesg.4.18.0-14-generic

Then reboot on a non-faulty kernel and attach this file there, you can
delete it from your computer after that.

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

Title:
  4.18.0-14 doesn't boot past grub

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  4.18.0-14 doesn't boot past grub for me in thinkpad t510i. 4.18.0-13
  worked fine. I had to revert back  to 4.15 kernel. I'm using a distro
  that is based off of Ubuntu 18.04.

  System info:
  CPU:Intel(R) Core(TM) i5 CPU   M 520  @ 2.40GHz
  4 cores/threads
  2400.00 MHz
  RAM:7.59 GiB

  I'm not sure how to provide crash info, as the kernel doesn't boot.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=fcc2ec6a-a02c-4188-ac0d-a8f924741962
  InstallationDate: Installed on 2019-01-10 (18 days ago)
  InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181130
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4349BR8
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=3478dfd0-edae-424a-a34f-9f230cb9cacc ro quiet splash
  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:  tessa
  Uname: Linux 4.15.0-44-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4349BR8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4349BR8:pvrThinkPadT510:rvnLENOVO:rn4349BR8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4349BR8
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2019-01-30 Thread bam

It's not clear from the description what is the problem exactly?
I have similar symptoms with "unknown main item tag 0x0" message after timeout.

But my problem is that bluetooth keyboard disconnects on timeout (which
is normal), but then, on the first key press it's just loss, while the
keyboard reconnects successfully.

It doesn't occurs on the same system with Windows 10 - the key doesn't
lost on reconnect.

I wonder if it can be the same problem.

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1813955] Re: CONFIG_TEST_BPF is disabled

2019-01-30 Thread Thadeu Lima de Souza Cascardo

** Description changed:

- This makes some of our tests fail or be skipped.
+ [Impact]
+ Our bpf testing will fail or be skipped without notice. So, real bpf failures 
might end up being missed.
+ 
+ [Test case]
+ Both ADT and SRU will end up testing the built module.
+ 
+ [Regression potential]
+ Our tests will start showing real failures we don't want to miss.

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

Title:
  CONFIG_TEST_BPF is disabled

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  Our bpf testing will fail or be skipped without notice. So, real bpf failures 
might end up being missed.

  [Test case]
  Both ADT and SRU will end up testing the built module.

  [Regression potential]
  Our tests will start showing real failures we don't want to miss.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2019-01-30 Thread Marcelo Cerri

https://lists.ubuntu.com/archives/kernel-team/2019-January/098154.html

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  In Progress
Status in linux source package in Cosmic:
  In Progress

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:

[Kernel-packages] [Bug 1811093] Re: Bogus "Out of Memory" compiz invoked oom-killer

2019-01-30 Thread Craig

So far, no oom-killer problems with Xenial HWE in production.  Newer
kernel (Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18).  Not sure if it
matters, but still using the proprietary Nvidia driver, but it may be a
newer version.  Same version of compiz (0.9.12.3).

If you do not hear from us further, Xenial HWE channel solved the
problem.

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

Title:
  Bogus "Out of Memory" compiz invoked oom-killer

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This has happened five times in the past week (four times in the past
  36 hours):

kernel: compiz invoked oom-killer:

  There is plenty of free core memory and almost no swap in use when it
  happens.  This is Xenial with kernel version is 4.4.0-141, which
  contains fix to previously reported bug #1655842 "Out of Memory"
  oom-killer bug.  I only have one week of logs to go by, which contain
  five occurrences.  It has happened four times in the past 36 hours.
  Sometimes it happens right after logging into the unity / lighdm
  desktop (three out of five times), but not always.  In four out of
  five occurrences a postgres job was running and oom-killer killed
  postgres.  In the one other instance, postgres was quietly idle in the
  background and oom-killer killed Thunderbird.  Kernel messages in
  syslog from five occurrences:

  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=2, oom_score_adj=0
  compiz invoked oom-killer: gfp_mask=0x24040c0, order=3, oom_score_adj=0

  Additional info:

  $> lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  $> cat /proc/version_signature
  Ubuntu 4.4.0-141.167-generic 4.4.162

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

-- 
Mailing list: https://launchpad.net/~kernel-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-30 Thread andyczerwonka

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

Delll 5530 and the TB16. Works great with 4.15.0-43, freezes with
4.15.0-44. Had to revert.

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

[Kernel-packages] [Bug 1811860] Re: Display ports on Lenovo docking station stopped working after upgrade of linux-firmware 1.173.2 -> 1.173.3

2019-01-30 Thread Lars Skjærlund

I'm not hit by the kernel bug - I haven't tried installing kernel
4.15.0.44 yet. But some of my colleagues has - and opened bug [bug
1813663|https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663] in
return. We have a lot of rather new Lenovo laptops here...

My running config is still:

linux-image-generic   4.15.0.43.45
linux-firmware1.173.2

If I upgrade linux-firmware from 1.173.2 to 1.173.3, my external monitor
stops working. If I downgrade the same package, my monitor starts
working again.

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

Title:
  Display ports on Lenovo docking station stopped working after upgrade
  of linux-firmware 1.173.2 -> 1.173.3

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Carbon X1 running on Lenovo Thinkpad Ultra Dock

  I have only been able to attach a single monitor to the docking
  station before the upgrade of linux-firmware. After todays upgrade
  from 1.173.2 to 1.173.3, none of the outputs work anymore.

  The Ultra Dock has two DP, an HDMI, and a VGA output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.3
  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: Tue Jan 15 16:31:39 2019
  Dependencies:
   
  InstallationDate: Installed on 2018-12-03 (42 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1813509] Re: [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

2019-01-30 Thread P.D.

Is this the same issue as my issue here?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657

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

Title:
  [i915] NULL pointer on Linux 4.18.0-14-generic / cosmic

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After updated an old laptop to Ubuntu Cosmic (was running Xenial
  before) the graphic hangs at startup, nothing is displayed but a grey
  screen (grub residual), note that the recovery boot option using
  `nodmodeset` displays a text console and I'm still able to log-in over
  a serial tty on normal boot so kernel is alive but computer is not
  usable due to lack graphic support.

  Computer is a Thinkpad X61 Tablet plugged on an X6 Tablet UltraBase
  - http://www.thinkwiki.org/wiki/Category:X61_Tablet
  - http://www.thinkwiki.org/wiki/ThinkPad_X6_Tablet_UltraBase
  GPU is an Intel GMA X3100
  - http://www.thinkwiki.org/wiki/Intel_Graphics_Media_Accelerator_X3100

  Some information:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.10
  Release:  18.10
  Codename: cosmic

  # uname -a
  Linux arwen 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # lspci -vvv -nn -s 00:02.0
  00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) 
(prog-if 00 [VGA controller])
Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  8b 52 
08 48 c7 40 0c 00 00 00 00 83 ca 04 89 50 08 48 8d 50 14 
  [2.709180] RSP: 0018:c2718067b978 EFLAGS: 00010287
  [2.709180] RAX: c27190303000 RBX: 9e5533e87200 RCX: 
c27190303044
  [2.709180] RDX:  RSI: 01a8 RDI: 
0150
  [2.709180] RBP: c2718067b988 R08: 0001 R09: 
0002
  [2.709180] R10: 0001 R11: 9e5533e87200 R12: 
0202
  [2.709180] R13: 9e5533e87200 R14: 9e553380ac00 R15: 
9e5533ab8000
  [2.709180] FS:  7fd9f63c88c0() GS:9e557e40() 
knlGS:
  [2.709180] CS:  0010 DS:  ES:  CR0: 80050033
  [2.709180] CR2: 0008 CR3: 34302000 CR4: 
06f0
  [2.709180] Call Trace:
  [2.709180]  i915_request_alloc+0x24e/0x370 [i915]
  [2.709180]  i915_gem_init+0x26b/0x470 [i915]
  [2.709180]  i915_driver_load+0xab8/0xd80 [i915]
  [2.709180]  ? mutex_lock+0x12/0x30
  [2.709180]  i915_pci_probe+0x46/0x60 [i915]
  [2.709180]  local_pci_probe+0x46/0x90
  [2.709180]  pci_device_probe+0x11c/0x1a0
  [2.709180]  driver_probe_device+0x2e3/0x460
  [2.709180]  __driver_attach+0xe4/0x110
  [2.709180]  ? driver_probe_device+0x460/0x460
  [2.709180]  bus_for_each_dev+0x74/0xb0
  [2.709180]  ? kmem_cache_alloc_trace+0x1c4/0x1d0
  [2.709180]  driver_attach+0x1e/0x20
  [2.709180]  bus_add_driver+0x159/0x230
  [2.709180]  ? 0xc0474000
  [2.709180]  driver_register+0x70/0xc0
  [2.709180]  ? 0xc0474000
  [2.709180]  __pci_register_driver+0x57/0x60
  [2.709180]  i915_init+0x55/0x58 [i915]
  [2.709180]  do_one_initcall+0x4a/0x1c4
  [2.709180]  ? _cond_resched+0x19/0x30
  [2.709180]  ? kmem_cache_alloc_trace+0xb8/0x1d0
  [2.709180]  ? do_init_module+0x27/0x220
  [2.709180]  do_init_module+0x60/0x220
  [2.709180]  load_module+0x14f4/0x1890
  [2.709180]  __do_sys_finit_module+0xbd/0x120
  [2.709180]  ? __do_sys_finit_module+0xbd/0x120
  [2.709180]  __x64_sys_finit_module+0x1a/0x20
  [2.709180]  do_syscall_64+0x5a/0x110
  [2.709180]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.709180] RIP: 0033:0x7fd9f6e4d219
  [2.709180] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48 
  [2.709180] RSP: 002b:7ffc11865868 EFLAGS: 0246 ORIG_RAX: 
0139
  [2.709180] RAX: ffda RBX: 5580d38f98c0 RCX: 
7fd9f6e4d219
  [2.709180] RDX:  RSI: 7fd9f6d31cad RDI: 
0012
  [2.709180] RBP: 7fd9f6d31cad R08:  R09: 

  [2.709180] R10: 0012 R11: 0246 R12: 

  [2.709180] R13: 5580d3913ae0 R14: 0002 R15: 
5580d38f98c0
  [2.709180] Modules linked in: gpio_ich i915(+) i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sdhci_pci sysimgblt

[Kernel-packages] [Bug 1813795] Re: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel

2019-01-30 Thread limod

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

I have the same issue with a Thinkpad T440p. My external monitors
connected via the dockingstation remain black after booting and also
after i lock my computer. The internal monitor works for booting, but as
soon as i lock my computer, it also remains black.

No issues with 4.15.0-43

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

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

[Kernel-packages] [Bug 1690085]

2019-01-30 Thread thangalin

(In reply to Borislav Petkov from comment #511)
> 7. install kernel, needs root
> # make modules_install install

$ sudo make modules_install install
  ...
  INSTALL virt/lib/irqbypass.ko
  DEPMOD  4.20.5-dirty
sh ./arch/x86/boot/install.sh 4.20.5-dirty arch/x86/boot/bzImage \
System.map "/boot"
Cannot find LILO.

That's a misleading error message as LILO isn't installed on the system,
but the new kernel was copied:

$ ll /boot
-rw-r--r--  1 root root  5851008 Jan 29 22:40 vmlinuz

GRUB seems to have loaded it fine.

See attached dmesg-acpi-dump-cstates.txt for details.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" -

[Kernel-packages] [Bug 1690085]

2019-01-30 Thread thangalin

Created attachment 280867
dmesg log after rebooting with acpi-dump-cstates patch

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list:

[Kernel-packages] [Bug 1776563]

2019-01-30 Thread eutychios23

I dont think so, but with noapic i think only 13 aml tables load instead
of the 14 available,so you might get acpi problems with suspend/resume
or cpu powersave features(at least that's what i get).Try running gentoo
or calculate linux and test acpi and apic.Ideally "physical flat" apic
model chosen by kernel config of those distros works fine in my case and
all 14 aml tables load.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1690085]

2019-01-30 Thread desouzalauren

Bugs are sign of success product or any software because it makes
product more effective and perfect to use with the expert’s solutions
and user’s feedback. Thanks for finding bug on random soft lockup on new
Ryzen build.

Lauren,
https://www.cvfolks.co.uk/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh

[Kernel-packages] [Bug 1776563]

2019-01-30 Thread to_load

Are these (other than noapic) workarounds really enable APIC controller? With 
acpi=noirq only PIC and MSI entries present in /proc/interrupts. So I assume 
acpi=off does the same. While noapic obviously disables APIC but works fine for 
me.
Looks like ivrs_ioapic... enables APIC, but in my case system is very slow and 
even not always boots.
Is disabled APIC have significant drawbacks (while most of devices placed on 
MSI-routed PCI lanes)?

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

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

This change was made by a bot.

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

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

Title:
  T480: closed lid and touchpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After closing the lid and working with externals screens and mouse and
  keyboard, the mouse cursor jumps. The effect is caused by touchpad:
  the workaround is to completely disable it in settings.

  
  This bug is 4.15.0-44 kernel specific. With the previous version 4.15.0-43 
the problem was not observed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  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/controlC1:  afiergol   9976 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   9976 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   9976 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 30 17:29:35 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (300 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1
  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-08-22 (161 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1799388] Re: TM (Hardware Transactional Memory) instructions halt application on baremetal POWER9 DD2.1

2019-01-30 Thread Manoj Iyer

This patch was picked up in Cosmic
http://bugs.launchpad.net/bugs/1810820 via updates, and should be
available in the latest bionic-hwe kernel. Could you please test with
the bionic-hwe kernel to see if this is still an 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/1799388

Title:
  TM (Hardware Transactional Memory) instructions halt application on
  baremetal POWER9 DD2.1

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-10-15 
08:55:55 ==
  +++ This bug was initially created as a clone of Bug #167756 +++

  ---Problem Description---
  TM (Hardware Transactional Memory) instructions halt application on baremetal 
POWER9 DD2.1
   
  Contact Information = grom...@br.ibm.com 
   
  ---Additional Hardware Info---
  POWER9 DD2.1 (pvr 004e 1201) baremetal. Witherspoon. 

   
  Machine Type = POWER9 DD2.1 (pvr 004e 1201) baremetal 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Currently TM (Hardware Transactional Memory) on baremetal POWER9 DD2.1 (pvr 
004e 1201) with the latest firmware [1] (Firmware level [2] was also tested 
with the same result) and running Linux from Linus' upstream tree [3] or 
powerpc/next branch [4] is not working as expected. Once a TM instruction is 
executed in a process (any instruction), the process halts completely and has 
to be killed.

  A simple test case is to execute a 'tend.' which accordingly to POWER8
  behaviour and the ISA v3.00 if executed "in Non-transactional state is
  treated as a no-op." [5]. It means that the instruction in the test
  case below should be treated simply as a 'nop' instruction and the
  process would terminate normally but instead it halts and the process
  never terminates:

  root@io83:~/gromero# cat t.c
  int main() { asm ("tend.;"); }
  root@io83:~/gromero# make t
  make: 't' is up to date.
  root@io83:~/gromero# ./t
  ^C
  

  Ubuntu stock kernel 4.15.0-20-generic was also tested with the same
  result.

  I confirmed with Erich Hauptli (FW team) that FW stack levels [1]
  contain all the TM fixes we have at the moment.

  Thus, that issue affects any application that uses TM on a baremetal
  POWER9 DD2.1 (pvr 004e 1201).

  
  [1] 
  IBM-witherspoon-ibm-OP9_v1.19_1.160
  op-build-v1.21.2-255-g6ad1636-dirty
  buildroot-2017.11-5-g65679be
  skiboot-v5.10.5-op910-1
  hostboot-ed53939
  linux-4.14.24-openpower1-paed97e8
  petitboot-v1.6.6-p41a158a
  machine-xml-4af
  occ-ef5d466
  hostboot-binaries-6a92b6d
  capp-ucode-p9-dd2-v3
  sbe-7e02c23

  [2]
  open-power-witherspoon-v1.22-82-gebe1295-dirty
buildroot-2018.02.1-6-ga8d11267c2
skiboot-v6.0-rc1
hostboot-d9bf361-p6755b85
occ-f741c41
linux-4.16.7-openpower1-p945838d
petitboot-v1.7.1-pd695626
machine-xml-7cd20a6
hostboot-binaries-53aece6
capp-ucode-p9-dd2-v4
sbe-8e0105e
hcode-hw050318a.op920

  [3] https://github.com/torvalds/linux.git (master)
  [4] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git (next) 
  [5] Power ISA - Book II, p. 894
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: any tool using TM instruction set 

  Userspace rpm: not relevant 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for grom...@br.ibm.com: 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  The following patch fixes this issue:

  http://patchwork.ozlabs.org/patch/968375/

  Author: Michael Neuling 
  Date:   Tue Sep 11 13:07:56 2018 +1000

  powerpc/tm: Fix HFSCR bit for no suspend case
  
  Currently on P9N DD2.1 we end up taking infinite TM facility
  unavailable exceptions on the first TM usage by userspace.
  
  In the special case of TM no suspend (P9N DD2.1), Linux is told TM is
  off via CPU dt-ftrs but told to (partially) use it via
  OPAL_REINIT_CPUS_TM_SUSPEND_DISABLED. So HFSCR[TM] will be off from
  dt-ftrs but we need to turn it on for the no suspend case.
  
  This patch fixes this by enabling HFSCR TM in this case.
  
  Cc: sta...@vger.kernel.org # 4.15+
  Signed-off-by: Michael Neuling 

  == Comment: #2 - Michael Ranweiler  - 2018-10-15 
13:52:13 ==
  This is in the powerpc -next branch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd9a8c5a87395b6f05552c3b44e42fdc95760552

To manage notifications

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

2019-01-30 Thread Grzegorz Korba

I had the same issue on Dell Latitude E5570, reverted to
4.15.0-43-generic just now. Didn't try v45 yet, since it's unofficial
and not signed, AFAIS. Looking forward for an actual fix.

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

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 1813956] Status changed to Confirmed