[Kernel-packages] [Bug 1825322] Re: linux: -proposed tracker

2019-04-18 Thread Timo Aaltonen
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1825324 (bionic/linux-oem-osp1)
+ 
+ -- swm properties --

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1825324 (bionic/linux-oem-osp1)

  -- swm properties --

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

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


[Kernel-packages] [Bug 1824963] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker

2019-04-18 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1825324 ***
https://bugs.launchpad.net/bugs/1825324

** This bug has been marked a duplicate of bug 1825324
   linux-oem-osp1:  -proposed tracker

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

Title:
  linux-oem-osp1: 5.0.0-1004.5 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1824819

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

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


[Kernel-packages] [Bug 1825324] [NEW] linux-oem-osp1: 5.0.0-1004.5 -proposed tracker

2019-04-18 Thread Timo Aaltonen
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1824819
phase: Ready for Promote to Proposed
phase-changed: Thursday, 18. April 2019 08:49 UTC
reason:
  prepare-package: Pending -- Ready
  prepare-package-meta: Pending -- Ready
  prepare-package-signed: Pending -- Ready
  promote-to-proposed: Pending -- ready for review

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: New


** Tags: bionic block-proposed block-proposed-bionic 
kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1824819 kernel-sru-cycle-d2019.04.15-2

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-s

[Kernel-packages] [Bug 1825322] [NEW] linux: -proposed tracker

2019-04-18 Thread Timo Aaltonen
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

backports: bug 1825324 (bionic/linux-oem-osp1)

-- swm properties --

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-2

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-2

** Changed in: kernel-sru-workflow
   Status: New => In Progress

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow 

[Kernel-packages] [Bug 1824963] [NEW] linux-oem-osp1: 5.0.0-1004.5 -proposed tracker

2019-04-16 Thread Timo Aaltonen
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

-- swm properties --
kernel-stable-master-bug: 1824819

** Affects: kernel-sru-workflow
 Importance: Undecided
 Status: New

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: New


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1824819 kernel-sru-cycle-d2019.04.15-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

[Kernel-packages] [Bug 1824922] Re: [Graphics] CometLake graphics support

2019-04-15 Thread Timo Aaltonen
commit 298d6aaf6d80ac889ce5b871da715a9a3d9ad7b0
Author: Anusha Srivatsa 
Date:   Fri Mar 29 11:17:27 2019 +0200

drm/i915/cml: Introduce Comet Lake PCH

BugLink: http://bugs.launchpad.net/bugs/1821863

Comet Lake PCH is based off of Cannon Point(CNP).
Add PCI ID for Comet Lake PCH.

v2: Code cleanup (DK)

v3: Comment cleanup (Jani)

Cc: Jani Nikula 
Cc: Dhinakaran Pandiyan 
Cc: Rodrigo Vivi 
Signed-off-by: Anusha Srivatsa 
Reviewed-by: Rodrigo Vivi 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20190318200133.9666-2-anusha.sriva...@intel.com
(cherry-picked from drm-intel-next commit 
729ae330a0f2e270db2ca70c06a83d0aa2776288)
Signed-off-by: Timo Aaltonen 
Signed-off-by: Thadeu Lima de Souza Cascardo 


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

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

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

Title:
  [Graphics] CometLake graphics support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:

  a new PCIID is added to support CometLake graphics. Please add it into
  19.04 if possible.

  commit 729ae330a0f2e270db2ca70c06a83d0aa2776288

  Target Release: 19.04
  Target Kernel: 5.1-rc6

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

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


[Kernel-packages] [Bug 1822026] Re: [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code)

2019-04-15 Thread Timo Aaltonen
The commit will be reverted due to 1824677, so reopening until a patch
with a smaller impact will be applied

** Changed in: linux (Ubuntu Disco)
   Status: Fix Released => 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/1822026

Title:
  [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes
  or cannot complete install when nouveau driver is loaded (crashing in
  GP100 code)

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

Bug description:
  When I boot the Disco 19.04 beta live USB, I can see a lot of errors
  related to nouveau in dmesg.

  Because of this, `lspci` freezes, so reporting an issue is impossible
  either with ubuntu-bug or sosreport (in both cases, the log gathering
  stops when trying to get the output from lspci).

  In addition, when nouveau is enabled:

  - the touchpad becomes unresponsive or behaves in a very weird way (slowing 
down, jumping), forcing me to use an external mouse or the little pointer in 
the middle of the keyboard.
  - the device cannot be powered off or restarted. It freezes and nothing can 
be done (I tried SysRq+REISUB to no avail)

  To avoid this issue, I need to launch the live USB with the following
  command line:

  $ cat /proc/cmdline
  BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

  (that is, add `modprobe.blacklist=nouveau` to the command line in
  Grub)

  In the BIOS, I activated both GPUs (Intel and nvidia), which is the
  default settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.7
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 03:23:52 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash modprobe.blacklist=nouveau ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1824677] Re: Display only has 640x480

2019-04-15 Thread Timo Aaltonen
** Description changed:

+ [Impact]
+ ("older") NVIDIA hw will boot with a non-optimal resolution due to the change 
to disable nouveau.modeset by default. The patch will be changed later to apply 
only to a subset of NVIDIA hw, but for disco the commit should be reverted.
+ 
+ [Test case]
+ boot a kernel with the revert
+ 
+ [Regression potential]
+ bug 1822026 will be reopened, no other known regressions
+ 
+ 
+ --
+ 
  Upgraded kernel available.
  
  Restarted to 640x480 display.
  
  No other resolutions apparently available.
  
  Rebooted to previous kernel - display resolution now correct.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 14 06:20:02 2019
  DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
-Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
+  NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
+    Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
  InstallationDate: Installed on 2018-08-27 (229 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180824)
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.sku: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-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/1824677

Title:
  Display only has 640x480

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

Bug description:
  [Impact]
  ("older") NVIDIA hw will boot with a non-optimal resolution due to the change 
to disable nouveau.modeset by default. The patch will be changed later to apply 
only to a subset of NVIDIA hw, but for disco the commit should be reverted.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  bug 1822026 will be reopened, no other known regressions

  
  --

  Upgraded kernel available.

  Restarted to 640x480 display.

  No other resolutions apparently available.

  Rebooted to previous kernel - display resolution now correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 14 06:20:02 2019
  DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” 

[Kernel-packages] [Bug 1824677] Re: Display only has 640x480

2019-04-15 Thread Timo Aaltonen
we'll revert the change for now

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
   Status: 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/1824677

Title:
  Display only has 640x480

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

Bug description:
  [Impact]
  ("older") NVIDIA hw will boot with a non-optimal resolution due to the change 
to disable nouveau.modeset by default. The patch will be changed later to apply 
only to a subset of NVIDIA hw, but for disco the commit should be reverted.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  bug 1822026 will be reopened, no other known regressions

  
  --

  Upgraded kernel available.

  Restarted to 640x480 display.

  No other resolutions apparently available.

  Rebooted to previous kernel - display resolution now correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 14 06:20:02 2019
  DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160]
  InstallationDate: Installed on 2018-08-27 (229 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180824)
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.sku: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

2019-04-14 Thread Timo Aaltonen
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Confirmed

** Description changed:

- On my Dell XPS 9575, I get a black screen on boot when running the 19.04
- live image, OR after updating from 18.10 to 19.04.  It appears to be a
- kernel related bug that was introduced in 5.0 that is affected by
- certain laptop panels not conforming to their stated specifications.
+ [Impact]
+ On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live 
image, OR after updating from 18.10 to 19.04.  It appears to be a kernel 
related bug that was introduced in 5.0 that is affected by certain laptop 
panels not conforming to their stated specifications.
  
  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.
  
  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:
  
  https://bugs.freedesktop.org/show_bug.cgi?id=109959
  
  And the patch here:
  
  https://patchwork.freedesktop.org/patch/296411/
  
  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems otherwise.
  I was able to get the live image booted by adding the nomodeset kernel
  parameter to grub, so as a work around you can use this approach to
  install.
+ 
+ [Test case]
+ boot a kernel with the revert
+ 
+ [Regression potential]
+ shouldn't be any, since this reverts to what was used on kernels before 5.0

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

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

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

Bug description:
  [Impact]
  On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live 
image, OR after updating from 18.10 to 19.04.  It appears to be a kernel 
related bug that was introduced in 5.0 that is affected by certain laptop 
panels not conforming to their stated specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  shouldn't be any, since this reverts to what was used on kernels before 5.0

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

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


[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-04-14 Thread Timo Aaltonen
** Changed in: xorg-server (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-04-13 Thread Timo Aaltonen
the reason why it hasn't landed yet is that there have been other bugs
that meant the kernel had to be respun a few times, but 5.0.0-11.12 is
finally in proposed and should be the final kernel for the release..

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-12 Thread Timo Aaltonen
the disco kernel being prepared does enable bochs again, but kmod still
needs to be fixed.. there's no mechanism for arch-specific blacklisting
(right now at least), but the kernel option could still be disabled for
ppc if absolutely necessary

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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


[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-12 Thread Timo Aaltonen
right, so OTOH the old regression on ppc hasn't been fully verified yet,
but blacklisting bochs_drm causes 1823152 on x86 which surely is more
important than ppc..

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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


[Kernel-packages] [Bug 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker

2019-04-12 Thread Timo Aaltonen
** Summary changed:

- linux-oem-osp1:  -proposed tracker
+ linux-oem-osp1: 5.0.0-1003.4 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

Title:
  linux-oem-osp1: 5.0.0-1003.4 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1824383
  phase: Packaging
  phase-changed: Friday, 12. April 2019 08:11 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1823581] Re: Multi-touch screen test of checkbox failed on Disco 19.04

2019-04-11 Thread Timo Aaltonen
or rather bug 1774242

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

Title:
  Multi-touch screen test of checkbox failed on Disco 19.04

Status in linux package in Ubuntu:
  Invalid
Status in xf86-input-wacom package in Ubuntu:
  New
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Summary: I use a Dell Precision 5530 (I+N). The tests of checkbox
  failed: 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-
  zoom

  Steps to reproduce:
  1. Install checkbox
  $ sudo add-apt-repository ppa:hardware-certification/public
  $ sudo apt-get update
  $ sudo apt-get install checkbox-ng plainbox-provider-resource-generic 
plainbox-provider-certification-client plainbox-provider-checkbox
  2. Run the test cases - 3-touch-tap, 4-touch-tap, multitouch-rotate and 
multitouch-zoom via checkbox
  $ checkbox-cli

  Expected result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
passed
  Actual result:
  The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom 
failed

  Additional Information:
  The tests can be passed on XPS 13 9380

  Failure rate: 100%

  -

  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  system-manufacturer: Dell Inc.
  bios-version: 1.6.0
  CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x)
  system-product-name: Precision 5530
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2343 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-29 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 004: ID 0c45:671d Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5530
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=8e4bee3f-6d32-4221-8bd7-7cdbfcf163b7 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1824008] Re: linux-oem-osp1: -proposed tracker

2019-04-09 Thread Timo Aaltonen
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ -- swm properties --
+ kernel-stable-master-bug: 1823936

** Tags added: kernel-sru-backport-of-1823936

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Summary changed:

- linux-oem-osp1:  -proposed tracker
+ linux-oem-osp1: 5.0.0-1002.3 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

Title:
  linux-oem-osp1: 5.0.0-1002.3 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1823936

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

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


[Kernel-packages] [Bug 1823936] Re: linux: 5.0.0-10.11 -proposed tracker

2019-04-09 Thread Timo Aaltonen
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: bug 1823224 (bionic/linux-hwe-edge), bug 1823227 
(bionic/linux-oem-osp1)
+ backports: bug 1823224 (bionic/linux-hwe-edge)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 09. April 2019 13:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: bug 1823224 (bionic/linux-hwe-edge)
+ backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 09. April 2019 13:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux: 5.0.0-10.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1823224 (bionic/linux-hwe-edge), bug 1824008 
(bionic/linux-oem-osp1)
  derivatives: bug 1823218 (linux-raspi2), bug 1823219 (linux-aws), bug 1823220 
(linux-azure), bug 1823221 (linux-gcp), bug 1823222 (linux-kvm), bug 1823933 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 09. April 2019 13:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker

2019-04-09 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1824008 ***
https://bugs.launchpad.net/bugs/1824008

** Tags removed: kernel-sru-backport-of-1823936

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-master-bug: 1823936
  phase: Promote to Proposed
  phase-changed: Tuesday, 09. April 2019 13:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

** This bug has been marked a duplicate of bug 1824008
   linux-oem-osp1:  -proposed tracker

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

Title:
  linux-oem-osp1: 5.0.0-1001.2 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Tuesday, 09. April 2019 13:32 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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


[Kernel-packages] [Bug 1824008] [NEW] linux-oem-osp1: 5.0.0-1002.3 -proposed tracker

2019-04-09 Thread Timo Aaltonen
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

-- swm properties --
kernel-stable-master-bug: 1823936

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1823936 kernel-sru-cycle-d2019.04.04-2

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ub

[Kernel-packages] [Bug 1793004] Re: package linux-modules-4.15.0-1018-oem (not installed) failed to install/upgrade: unable to open '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drx

2019-04-09 Thread Timo Aaltonen
sounds like your disk was full

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-modules-4.15.0-1018-oem (not installed) failed to
  install/upgrade: unable to open
  '/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-
  frontends/drxd.ko.dpkg-new': Operation not permitted

Status in linux-oem package in Ubuntu:
  Invalid

Bug description:
  N/A

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-4.15.0-1018-oem (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-1017.20-oem 4.15.18
  Uname: Linux 4.15.0-1017-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 17 06:40:58 2018
  DuplicateSignature:
   package:linux-modules-4.15.0-1018-oem:(not installed)
   Unpacking linux-modules-4.15.0-1018-oem (4.15.0-1018.21) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-U05ilT/2-linux-modules-4.15.0-1018-oem_4.15.0-1018.21_amd64.deb
 (--unpack):
unable to open 
'/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to open 
'/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new':
 Operation not permitted
  InstallationDate: Installed on 2018-08-30 (18 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: linux-oem
  Title: package linux-modules-4.15.0-1018-oem (not installed) failed to 
install/upgrade: unable to open 
'/lib/modules/4.15.0-1018-oem/kernel/drivers/media/dvb-frontends/drxd.ko.dpkg-new':
 Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1823428] Re: linux-oem ftbfs in disco

2019-04-09 Thread Timo Aaltonen
1035 seems to have built fine on disco & cosmic

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

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

Title:
  linux-oem ftbfs in disco

Status in linux-oem package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924465/buildlog_ubuntu-disco-amd64
  .linux-oem_4.15.0-1034.39_BUILDING.txt.gz

HOSTLD  scripts/mod/modpost
HOSTCC  scripts/selinux/genheaders/genheaders
  In file included from 
/<>/scripts/selinux/genheaders/genheaders.c:19:
  /<>/security/selinux/include/classmap.h:247:2: error: #error New 
address family defined, please update secclass_map.
   #error New address family defined, please update secclass_map.
^
  make[6]: *** [scripts/Makefile.host:90: 
scripts/selinux/genheaders/genheaders] Error 1
  make[5]: *** [/<>/scripts/Makefile.build:606: 
scripts/selinux/genheaders] Error 2
  make[4]: *** [/<>/scripts/Makefile.build:606: scripts/selinux] 
Error 2
  make[3]: *** [/<>/Makefile:589: scripts] Error 2
  make[2]: *** [/<>/Makefile:278: __build_one_by_one] Error 2
  make[2]: Leaving directory '/<>/debian/build/build-oem'
  make[1]: *** [Makefile:146: sub-make] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules.d/2-binary-arch.mk:31: 
/<>/debian/stamps/stamp-prepare-tree-oem] Error 2

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

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


[Kernel-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on

2019-04-09 Thread Timo Aaltonen
excellent, thanks

** Changed in: linux-oem (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Often the VGA screen stops working after screen saver was on

Status in linux-oem package in Ubuntu:
  Fix Released

Bug description:
  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.

  There seems to be a kernel crash before as seen in the dmesg log.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
  Uname: Linux 4.15.0-1034-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 12:04:07 2019
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: Installed on 2019-02-12 (44 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9380
  ProcEnviron:
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem 
root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KTDY6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-04-08 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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


[Kernel-packages] [Bug 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker

2019-04-05 Thread Timo Aaltonen
** Summary changed:

- linux-oem-osp1:  -proposed tracker
+ linux-oem-osp1: 5.0.0-1001.2 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

Title:
  linux-oem-osp1: 5.0.0-1001.2 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1823228
  phase: Holding before Packaging
  phase-changed: Thursday, 04. April 2019 19:40 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

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


[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-04-05 Thread Timo Aaltonen
Ok, so xrdp in bionic builds modules for the xserver, which won't work
with the HWE xserver. These modules got since split from src:xrdp as
src:xorgxrdp. Note that xrdp in bionic did not have these modules, so
this issue is new with bionic HWE and wasn't expected.

So it does look like xrdp in bionic would need a HWE version. BTW, does
your xrdp-next built against HWE work with stock X?

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")

2019-04-05 Thread Timo Aaltonen
Your setup is anything but a typical one, and bugs should not be used to
"ask" how something works the way it does. You mentioned that the
"original" disco install always works fine, so I don't think there's a
valid bug here at all?

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-04-04 Thread Timo Aaltonen
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-04-04 Thread Timo Aaltonen
** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg-server (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/1821820

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

2019-04-04 Thread Timo Aaltonen
This should be a  bug in xserver, but since there's no fix in sight it's
best to revert the commit from kernel for now.

** Package changed: xserver-xorg-video-intel (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/1821820

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


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

2019-04-04 Thread Timo Aaltonen
** Bug watch added: freedesktop.org Bugzilla #110187
   https://bugs.freedesktop.org/show_bug.cgi?id=110187

** Also affects: dri via
   https://bugs.freedesktop.org/show_bug.cgi?id=110187
   Importance: Unknown
   Status: Unknown

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

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

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

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

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

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

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

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

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

  ---
  .tmp.unity_support_test.0:

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

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

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


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

2019-04-03 Thread Timo Aaltonen
more or less, though AIUI the xserver changes aren't necessary if the
kernel support is there

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

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

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

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

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

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

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

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

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

  ---
  .tmp.unity_support_test.0:

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

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

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


[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module

2019-04-03 Thread Timo Aaltonen
i915 is loaded just fine on your first journal log:

Mar 25 23:26:06 zlink2 kernel: [drm] Initialized i915 1.6.0 20181204 for
:00:02.0 on minor 0

but it's happening after lightdm is started, so I'd say it's lightdm
which is just being too hasty

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-04-03 Thread Timo Aaltonen
** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => 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/1821863

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  New
Status in xorg-server source package in Disco:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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


[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-03 Thread Timo Aaltonen
t-lamprecht/cascardo: are you able to reply to adam's question, so that
this could be enabled across the board and not just on !ppc?

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  New
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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


[Kernel-packages] [Bug 1822715] Re: Need a meta package to add necessary X stack support for Intel ICL to Bionic Edit

2019-04-02 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  Need a meta package to add necessary X stack support for Intel ICL to
  Bionic Edit

Status in linux-oem package in Ubuntu:
  Invalid

Bug description:
  - In preparation of the 18.04osp1 base image, we need to a meta
  package that adds necessary X stack support for Intel ICL to Bionic

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

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


[Kernel-packages] [Bug 1822715] Re: Need a meta package to add necessary X stack support for Intel ICL to Bionic Edit

2019-04-01 Thread Timo Aaltonen
you should just use xserver-xorg-hwe-18.04

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

Title:
  Need a meta package to add necessary X stack support for Intel ICL to
  Bionic Edit

Status in linux-oem package in Ubuntu:
  New

Bug description:
  - In preparation of the 18.04osp1 base image, we need to a meta
  package that adds necessary X stack support for Intel ICL to Bionic

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

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


[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-01 Thread Timo Aaltonen
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1795857

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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


[Kernel-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode

2019-03-30 Thread Timo Aaltonen
what's "tent" mode?

anyway, the screen rotation sensor or driver seems buggy

** Package changed: x11-xserver-utils (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/1804568

Title:
  click position is flipped to cursor position when in tent mode

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822267] Re: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response

2019-03-29 Thread Timo Aaltonen
** Information type changed from Proprietary to Public

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

Title:
  [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response

Status in amd:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  Raven 2 platform fails to boot on ubuntu 19.04 (disco) with kernel
  5.0.0. The issue is related to a fixed patch in linux-mainline about
  psp response code status.

  In some cases, psp response status is not 0 even there is no problem
  while the command is submitted. Some version of PSP FW doesn't write 0
  to that field. So here we would like to only print a warning instead
  of an error during psp initialization to avoid breaking hw_init and it
  doesn't return -EINVAL.

  Steps:
  1. Install Ubuntu 19.04 daily build on AMD Raven 2 platform (reproduced with 
2019.03.18 version)
  2. Reboot and it fails at kernel initialization.

  Current patch status:
  A patch has already accepted in the linux mainline. (id: 
466bcb75b0791ba301817cdadeed20398f2224fe)
  See: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=466bcb75b0791ba301817cdadeed20398f2224fe

  Backport status:
  A backport patch is available and verified.

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

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


[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-03-29 Thread Timo Aaltonen
** Changed in: linux (Ubuntu Bionic)
   Status: New => Invalid

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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


[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-03-29 Thread Timo Aaltonen
leaving cosmic out, this will only be needed in disco and bionic.

** Description changed:

+ [Impact]
+ 
  Please make it happen in the coming oem-kernel as there will be a flood
- of Intel CML platforms that would need it. Thank you.
+ of Intel Comet Lake (CML) platforms that would need it. Thank you.
  
  The same is needed for the rest of the stack.
+ 
+ [Test case]
+ 
+ Test that i915 graphics works on CML.
+ 
+ [Regression potential]
+ 
+ None really, these only add a bunch of new pci-id's across the stack.

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

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

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: libdrm (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Description changed:

  [Impact]
  
  Please make it happen in the coming oem-kernel as there will be a flood
  of Intel Comet Lake (CML) platforms that would need it. Thank you.
  
  The same is needed for the rest of the stack.
+ 
+ CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and
+ doesn't need other changes than pci-id's and support for the PCH
+ (similar to Cannon point, already supported by the kernel).
  
  [Test case]
  
  Test that i915 graphics works on CML.
  
  [Regression potential]
  
  None really, these only add a bunch of new pci-id's across the stack.

** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1821863

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

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

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


[Kernel-packages] [Bug 1817817] Please test proposed package

2019-03-29 Thread Timo Aaltonen
Hello AceLan, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.5 in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  To add power setting bin file for SAR support (QCA6174)

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  To meet the policy requirement of the RF radiation, we need to reduce the 
power of the device.

  [Fix]
  Qualcomm provides a new firmware for this.
  97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

  [Test]
  We can't verify it.

  [Regression Potential]
  Low, it's a fix from upstream.

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

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


[Kernel-packages] [Bug 1794055] Please test proposed package

2019-03-29 Thread Timo Aaltonen
Hello bugproxy, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.5 in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-03-29 Thread Timo Aaltonen
Hello James, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.5 in a few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi 

[Kernel-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

2019-03-29 Thread Timo Aaltonen
Is this a regression from older releases?

when you say that disabling switchable graphics makes it use nvidia, I'd
doubt that.. it should use intel then?

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

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

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.288619] ACPI: Skipping parse of AML opcode: 

[Kernel-packages] [Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"

2019-03-29 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1822026 ***
https://bugs.launchpad.net/bugs/1822026

** This bug has been marked a duplicate of bug 1822026
   [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or 
cannot complete install when nouveau driver is loaded (crashing in GP100 code)

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

Title:
  Laptop freezes after installation is finished when pressing "Restart
  Now"

Status in linux package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  As stated in lp:1822026, the Dell Precision 7530 I'm using is using
  nouveau graphics drivers by default when starting a live session, and
  this driver is prone to errors.

  One of the most annoying for a new user is the following:

  1. Boot into 19.04 live session
  2. Launch "Install Ubuntu 19.04" and go through the installation steps
  3. Once the install is done, the "Installation Complete" dialog is shown with 
two options: [Continue Testing][Restart Now]
  4. Press [Restart Now]

  Expected behaviour:

  4. The device restarts and boots into freshly installed Ubuntu 19.04.

  Actual behaviour:

  4. The device freezes and even the keyboard combination SysRq+REISUB
  doesn't do anything. User has to force shutdown the device by pressing
  Power button for a few seconds, remember to remove the USB drive, then
  manually start the device.

  All the hardware-related information is available in the sosreport
  attachment in lp:1822026:
  
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822026/+attachment/5249977/+files
  /sosreport-ubuntu-20190328033617.tar.xz

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

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


[Kernel-packages] [Bug 1822026] Re: Live USB freezes or cannot complete install when nouveau driver is loaded

2019-03-28 Thread Timo Aaltonen
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Live USB freezes or cannot complete install when nouveau driver is
  loaded

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I boot the Disco 19.04 beta live USB, I can see a lot of errors
  related to nouveau in dmesg.

  Because of this, `lspci` freezes, so reporting an issue is impossible
  either with ubuntu-bug or sosreport (in both cases, the log gathering
  stops when trying to get the output from lspci).

  In addition, when nouveau is enabled:

  - the touchpad becomes unresponsive or behaves in a very weird way (slowing 
down, jumping), forcing me to use an external mouse or the little pointer in 
the middle of the keyboard.
  - the device cannot be powered off or restarted. It freezes and nothing can 
be done (I tried SysRq+REISUB to no avail)

  To avoid this issue, I need to launch the live USB with the following
  command line:

  $ cat /proc/cmdline
  BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

  (that is, add `modprobe.blacklist=nouveau` to the command line in
  Grub)

  In the BIOS, I activated both GPUs (Intel and nvidia), which is the
  default settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.7
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 03:23:52 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash modprobe.blacklist=nouveau ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822026] Re: Live USB freezes or cannot complete install when nouveau driver is loaded

2019-03-28 Thread Timo Aaltonen
upstream actually suggested earlier to disable nouveau modeset by
default, so that it would have to be explicitly enabled if needed.. and
it usually isn't, since it's more or less just getting in the way when
trying to get the system installed with the NVIDIA driver

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

Title:
  Live USB freezes or cannot complete install when nouveau driver is
  loaded

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I boot the Disco 19.04 beta live USB, I can see a lot of errors
  related to nouveau in dmesg.

  Because of this, `lspci` freezes, so reporting an issue is impossible
  either with ubuntu-bug or sosreport (in both cases, the log gathering
  stops when trying to get the output from lspci).

  In addition, when nouveau is enabled:

  - the touchpad becomes unresponsive or behaves in a very weird way (slowing 
down, jumping), forcing me to use an external mouse or the little pointer in 
the middle of the keyboard.
  - the device cannot be powered off or restarted. It freezes and nothing can 
be done (I tried SysRq+REISUB to no avail)

  To avoid this issue, I need to launch the live USB with the following
  command line:

  $ cat /proc/cmdline
  BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

  (that is, add `modprobe.blacklist=nouveau` to the command line in
  Grub)

  In the BIOS, I activated both GPUs (Intel and nvidia), which is the
  default settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.7
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 03:23:52 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash modprobe.blacklist=nouveau ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822026] Re: Live USB freezes or cannot complete install when nouveau driver is loaded

2019-03-28 Thread Timo Aaltonen
sorry, 5.1 won't help either, it's apparently a bug in the firmware and
the only way to "fix" it is to use nouveau.modeset=0

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

Title:
  Live USB freezes or cannot complete install when nouveau driver is
  loaded

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I boot the Disco 19.04 beta live USB, I can see a lot of errors
  related to nouveau in dmesg.

  Because of this, `lspci` freezes, so reporting an issue is impossible
  either with ubuntu-bug or sosreport (in both cases, the log gathering
  stops when trying to get the output from lspci).

  In addition, when nouveau is enabled:

  - the touchpad becomes unresponsive or behaves in a very weird way (slowing 
down, jumping), forcing me to use an external mouse or the little pointer in 
the middle of the keyboard.
  - the device cannot be powered off or restarted. It freezes and nothing can 
be done (I tried SysRq+REISUB to no avail)

  To avoid this issue, I need to launch the live USB with the following
  command line:

  $ cat /proc/cmdline
  BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

  (that is, add `modprobe.blacklist=nouveau` to the command line in
  Grub)

  In the BIOS, I activated both GPUs (Intel and nvidia), which is the
  default settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.7
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 03:23:52 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash modprobe.blacklist=nouveau ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822085] Re: Often the VGA screen stops working after screen saver was on

2019-03-28 Thread Timo Aaltonen
try linux-oem -1035 from bionic-proposed, it has ~50 commits backported
from 5.0 to i915 driver which should help with these issues

** Description changed:

  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.
  
  There seems to be a kernel crash before as seen in the dmesg log.
+ 
+ 
+ ProblemType: Bug
+ DistroRelease: Ubuntu 18.04
+ Package: xorg 1:7.7+19ubuntu7.1
+ ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
+ Uname: Linux 4.15.0-1034-oem x86_64
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ Date: Thu Mar 28 12:04:07 2019
+ DistUpgraded: Fresh install
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
+ DistroCodename: bionic
+ DistroVariant: ubuntu
+ DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
+Subsystem: Dell Device [1028:08af]
+ InstallationDate: Installed on 2019-02-12 (44 days ago)
+ InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
+ MachineType: Dell Inc. XPS 13 9380
+ ProcEnviron:
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1034-oem 
root=UUID=0b807479-b451-4f56-b9cc-307300b68200 ro quiet splash vt.handoff=1
+ SourcePackage: xorg
+ Symptom: display
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ dmi.bios.date: 02/14/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.1
+ dmi.board.name: 0KTDY6
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTDY6:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 13 9380
+ dmi.sys.vendor: Dell Inc.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.95-1~18.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
+ version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

Title:
  Often the VGA screen stops working after screen saver was on

Status in linux-oem package in Ubuntu:
  Incomplete

Bug description:
  I have two connected external monitors. They are connected through a
  Dell Dock W15. One is connected with VGA, the other with DP. Sometimes
  the VGA monitor complains about the resolution and will not work after
  the screen saver has been active (and putting the monitors to sleep).
  When shutting down the system, it then hangs and I have to force a
  shutdown with the power button.

  There seems to be a kernel crash before as seen in the dmesg log.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-1034.39-oem 4.15.18
  Uname: Linux 4.15.0-1034-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 12:04:07 2019
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-1034-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08af]
  InstallationDate: 

[Kernel-packages] [Bug 1822026] Re: Live USB freezes or cannot complete install when nouveau driver is loaded

2019-03-28 Thread Timo Aaltonen
please try mainline build of 5.1-rc from

http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

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

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

Title:
  Live USB freezes or cannot complete install when nouveau driver is
  loaded

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I boot the Disco 19.04 beta live USB, I can see a lot of errors
  related to nouveau in dmesg.

  Because of this, `lspci` freezes, so reporting an issue is impossible
  either with ubuntu-bug or sosreport (in both cases, the log gathering
  stops when trying to get the output from lspci).

  In addition, when nouveau is enabled:

  - the touchpad becomes unresponsive or behaves in a very weird way (slowing 
down, jumping), forcing me to use an external mouse or the little pointer in 
the middle of the keyboard.
  - the device cannot be powered off or restarted. It freezes and nothing can 
be done (I tried SysRq+REISUB to no avail)

  To avoid this issue, I need to launch the live USB with the following
  command line:

  $ cat /proc/cmdline
  BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

  (that is, add `modprobe.blacklist=nouveau` to the command line in
  Grub)

  In the BIOS, I activated both GPUs (Intel and nvidia), which is the
  default settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.7
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 03:23:52 2019
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash modprobe.blacklist=nouveau ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1822044] Re: Laptop freezes after installation is finished when pressing "Restart Now"

2019-03-28 Thread Timo Aaltonen
so this is another dupe of 1822026?

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

Title:
  Laptop freezes after installation is finished when pressing "Restart
  Now"

Status in linux package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  As stated in lp:1822026, the Dell Precision 7530 I'm using is using
  nouveau graphics drivers by default when starting a live session, and
  this driver is prone to errors.

  One of the most annoying for a new user is the following:

  1. Boot into 19.04 live session
  2. Launch "Install Ubuntu 19.04" and go through the installation steps
  3. Once the install is done, the "Installation Complete" dialog is shown with 
two options: [Continue Testing][Restart Now]
  4. Press [Restart Now]

  Expected behaviour:

  4. The device restarts and boots into freshly installed Ubuntu 19.04.

  Actual behaviour:

  4. The device freezes and even the keyboard combination SysRq+REISUB
  doesn't do anything. User has to force shutdown the device by pressing
  Power button for a few seconds, remember to remove the USB drive, then
  manually start the device.

  All the hardware-related information is available in the sosreport
  attachment in lp:1822026:
  
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822026/+attachment/5249977/+files
  /sosreport-ubuntu-20190328033617.tar.xz

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

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


[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-03-27 Thread Timo Aaltonen
** Summary changed:

- Need to add Intel CML related pci-id's to the oem-kernel
+ Need to add Intel CML related pci-id's

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** Description changed:

  Please make it happen in the coming oem-kernel as there will be a flood
  of Intel CML platforms that would need it. Thank you.
+ 
+ The same is needed for the rest of the stack.

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel CML platforms that would need it. Thank you.

  The same is needed for the rest of the stack.

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

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


[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-03-22 Thread Timo Aaltonen
please test on cosmic or disco

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => 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/1817225

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1815759] Re: Does not recognize connected HDMI monitor

2019-03-15 Thread Timo Aaltonen
The actual driver is in the kernel, which in your case is ancient

If 5.0 doesn't work, file a bug upstream and hope for the best

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  Does not recognize connected HDMI monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Strandely 'sudo lshw -c video' told nouveau is in use even if xserver-
  xorg-video-nouveau was not installed. With or without, HDMI does not
  work unlike with proprietary driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog: root: clean, 318243/1281120 files, 2346720/512 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Feb 13 14:16:02 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-140-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-141-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-143-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (1179 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (970) killed by TERM signal
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash 
vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 13 14:12:08 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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


[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+

2019-03-15 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

Title:
  i915: Backport watermark fixes for gen9+

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:

  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

  [Test case]
  Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware

  [Regression potential]
  The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

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

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


[Kernel-packages] [Bug 1817058] Re: Fix I219 doesn't get woken up after plugging ethernet cable

2019-03-15 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Fix I219 doesn't get woken up after plugging ethernet cable

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in linux-oem source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-oem source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Plugging ethernet cable doesn't work on new I219 after it runtime
  suspends to D3.

  [Fix] 
  Intel confirms that it only supports D0, so disable runtime power
  management to prevent it from entering D3.

  [Test]
  Once the patch applied, the device always stays at D0, which doesn't
  have this problem.

  [Regression Potential]
  Low. This doesn't introduce any functional change.

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

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


[Kernel-packages] [Bug 1818617] Re: [amdgpu] screen corruption when using touchpad

2019-03-15 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  [amdgpu] screen corruption when using touchpad

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  An OEM system is suffering from screen corruption when the touchpad is used. 
This would be fixed by backporting these commits from 4.18:

  ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
  6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.

  [Test case]
  boot a fixed kernel on the affected system, check that it doesn't suffer from 
the corruption

  [Regression potential]
  low, this has been upstream since 4.18, and AMD asked us to backport these

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

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


[Kernel-packages] [Bug 1817676] Re: r8169 doesn't get woken up by ethernet cable plugging, no PME generated

2019-03-15 Thread Timo Aaltonen
** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  r8169 doesn't get woken up by ethernet cable plugging, no PME
  generated

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Incomplete
Status in linux-oem source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Once r8169 (Realtek ethernet) and its root port enter to D3, plugging
  network cable doesn't wake r8169 up.

  [Fix]
  Revert "PCI/PME: Implement runtime PM callbacks".
  Quote the original commit message:
  "
  The commit tried to prevent root port waking up from D3cold immediately but
  looks like disabing root port PME interrupt is not the right way to fix
  that issue so revert it now.  The patch following proposes an alternative
  solution to that issue.
  "

  [Test]
  After applying the fix, plugging the ethernet cable can generate PME IRQ
  correctly, hence waking up r8169.

  [Regression Potential]
  Medium. The commits are relative new, rely on some PCI detail that I am
  not familiar with (PCI spec isn't publicly available).
  Fortunately we only need this fix for Unstable/OEM-B, so it won't hit
  most users if any regression happens.

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

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


[Kernel-packages] [Bug 1820031] Re: My Ubuntu 18.04 GUI seems frozen

2019-03-14 Thread Timo Aaltonen
the kernel driver "crashed", which is why the screen froze

You could try booting with i915.enable_ppgtt=0 to see if the bug goes
away, or a newer kernel. 4.18 is available via 'linux-image-generic-
hwe-18.04'.

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

Title:
  My Ubuntu 18.04 GUI seems frozen

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  This will possibly be a duplicate of Bug #1820028 or Bug #1820029 or
  Bug #1820030

  I was trying to report a frozen GUI over SSH. This is the second
  report that apport-cli generated when I ran it with xorg as the target
  package.  I made three four reports to see if different diagnostics
  were geneereated as Ihave no way of knowing what is causing the lock
  up at present.

  The symptoms I see are that I started running a go test last night and
  my GUI on Ubuntu 18.04 seems to have frozen. I cannot get the wireless
  mouse or keyboard to move anything on the display and the time shown
  on the clock matches when things froze last night.

  Before I made the report I looked for any process using high amounts
  of CUP with top and htop but spotted none. I tried to local a SIGTERM
  the go test process but that made no difference.

  

  I shall attempt to restart my desktop service

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 14 09:12:51 2019
  DistUpgraded: 2018-07-27 11:19:59,510 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
  InstallationDate: Installed on 2017-11-16 (482 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=473dc1b9-3a5c-4f95-8cc0-e3b0f628ca41 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: PuTTY X11 proxy: unable to connect to forwarded X server: Network 
error: Connection refused
   Error: unable to open display
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (229 days ago)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0811
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0811:bd09/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Mar 12 13:46:44 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2
  xserver.video_driver: modeset

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

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


[Kernel-packages] [Bug 1819692] Re: linux-oem: 4.15.0-1035.40 -proposed tracker

2019-03-14 Thread Timo Aaltonen
** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1035.40 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  kernel-stable-master-bug: 1819716
  phase: Ready for Packaging
  phase-changed: Wednesday, 13. March 2019 11:05 UTC
  reason:
prepare-package: Pending -- version not specified

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-13 Thread Timo Aaltonen
bionic was already fixed earlier by 18.2.2-0ubuntu1~18.04.2 in time for
18.04.2 release

cosmic got the exact same oneliner in 18.2.8-0ubuntu0~blah, and then
that was backported to bionic which reopened this bug. Requiring Alkis
to test this on cosmic is too much IMO, as it would involve first to set
up a school to use cosmic, then test remotely or ask folks over there to
report back... all for a oneliner.

Alkis, please correct me if I'm wrong..

** Description changed:

- Several schools reported black screens after normally updating their
- Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.
+ [Impact]
+ Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.
  
  Downgrading mesa fixes the problem.
  
  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915
  
  Unfortunately I can't find a lot of useful information, here are some bits:
-  * systemctl --failed says "gpu-manager" and "lightdm" have failed
-  * Xorg.log is clean: https://termbin.com/6l2b
-  * dmesg too: https://termbin.com/ip4e
-  * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
-  * If one runs `xinit` from ssh, it fails with:
+  * systemctl --failed says "gpu-manager" and "lightdm" have failed
+  * Xorg.log is clean: https://termbin.com/6l2b
+  * dmesg too: https://termbin.com/ip4e
+  * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
+  * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument
+ 
+ This is caused by mesa assuming that soft-pinning on GEN8+ is working
+ since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a
+ proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
+ sizes/pin flags, but that's left for future.
+ 
+ [Test case]
+ install fixed mesa or kernel, check that the regression is fixed
+ 
+ [Regression potential]
+ mesa: shouldn't be any, it just reverts the change to always soft-pin
+ (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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


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

2019-03-13 Thread Timo Aaltonen
** Description changed:

  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:
  
  0x3E98
  0x87C0
  
  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.
  
  [Test case]
- Check that the user session uses the proper driver on these systems.
+ Check that the user session uses the proper driver on these systems, if 
possible. Adding new pci-id's is a trivial change which can't regress existing 
hw.
  
  [Regression potential]
  none, these just add pci-id's and platform definitions

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

Title:
  Missing Intel GPU pci-id's

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

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

  0x3E98
  0x87C0

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

  [Test case]
  Check that the user session uses the proper driver on these systems, if 
possible. Adding new pci-id's is a trivial change which can't regress existing 
hw.

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

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

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


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

2019-03-13 Thread Timo Aaltonen
This was already fixed in bionic by 18.2.2-0ubuntu1~18.04.1, now the
same is included upstream in 18.2.8 which was upload to cosmic too as
well as to bionic via a new backport.

Again, I don't have the hardware (AML, WHL is broken atm), adding pci-
id's just allow the X driver to load the DRI driver, there is no
regression potential on other hw etc etc.

So in a way this bug should've been marked 'invalid' for cosmic and just
let it be part of 18.2.8 upstream version which is handled separately in
bug 1811225.. My bad for including it in the changelog.

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

Title:
  Missing Intel GPU pci-id's

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

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

  0x3E98
  0x87C0

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

  [Test case]
  Check that the user session uses the proper driver on these systems, if 
possible. Adding new pci-id's is a trivial change which can't regress existing 
hw.

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

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-12 Thread Timo Aaltonen
actually, bionic was already tested earlier, and the tested fix is a
one-line change to mesa which is still the same on 18.2.8 so marking
bionic verified.. and also cosmic since it's the exact same version
there, and cosmic kernel was also tested to be buggy

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-12 Thread Timo Aaltonen
** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-12 Thread Timo Aaltonen
Alkis, please test 18.2.8 for bionic and if possible, cosmic

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


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

2019-03-08 Thread Timo Aaltonen
Hello Agustin, or anyone else affected,

Accepted upower into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.7-2ubuntu0.18.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: upower (Ubuntu Bionic)
   Status: Incomplete => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  

[Kernel-packages] [Bug 1811692] Re: udev coldplug will interrupt makedumpfile

2019-03-08 Thread Timo Aaltonen
this is referenced in the cosmic backport, so needs SRU template, test
case etc

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

Title:
  udev coldplug will interrupt makedumpfile

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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


[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

2019-03-08 Thread Timo Aaltonen
needs SRU template, test case etc

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Fix Released

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  In Progress
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline 
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
 s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

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

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


[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+

2019-03-08 Thread Timo Aaltonen
** Description changed:

- 5.0 fixes screen flicker issues with new panel models and on hybrid
- machines, and Intel has prepared a backport for 4.15 which we can use.
- It consists of 50+ cherry-picked commits plus a handful of build fixes:
+ [Impact]
+ 5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:
  
  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15
  
- It's a big change which needs to be tested properly on a wide array of
- certified machines.
+ [Test case]
+ Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware
+ 
+ [Regression potential]
+ The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

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

Title:
  i915: Backport watermark fixes for gen9+

Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:

  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

  [Test case]
  Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware

  [Regression potential]
  The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

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

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


[Kernel-packages] [Bug 1818617] Re: [amdgpu] screen corruption when using touchpad

2019-03-07 Thread Timo Aaltonen
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Description changed:

- An OEM system is suffering from screen corruption when the touchpad is
- used. This would be fixed by backporting these commits from 4.18:
+ [Impact]
+ An OEM system is suffering from screen corruption when the touchpad is used. 
This would be fixed by backporting these commits from 4.18:
  
  ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
  6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.
+ 
+ [Test case]
+ boot a fixed kernel on the affected system, check that it doesn't suffer from 
the corruption
+ 
+ [Regression potential]
+ low, this has been upstream since 4.18, and AMD asked us to backport these

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

Title:
  [amdgpu] screen corruption when using touchpad

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  New

Bug description:
  [Impact]
  An OEM system is suffering from screen corruption when the touchpad is used. 
This would be fixed by backporting these commits from 4.18:

  ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
  6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.

  [Test case]
  boot a fixed kernel on the affected system, check that it doesn't suffer from 
the corruption

  [Regression potential]
  low, this has been upstream since 4.18, and AMD asked us to backport these

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

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


[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package

2019-03-07 Thread Timo Aaltonen
ajax gave a patch to fix selecting a better default bpp, so that'll fix
the server to start even without cirrus.ko

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-vesa
(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/1818879

Title:
  pull cirrus.ko into main kernel package

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vesa package in Ubuntu:
  Confirmed

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-05 Thread Timo Aaltonen
bionic has 4.18 backport now, installed with 18.04.2 image or manually
via 'linux-generic-hwe-18.04'

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

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

Title:
  VegaM support

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

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

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

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

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

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


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

2019-03-05 Thread Timo Aaltonen
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic

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

Title:
  Missing Intel GPU pci-id's

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

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

  0x3E98
  0x87C0

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

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

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

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-05 Thread Timo Aaltonen
please test the new mesa on bionic/cosmic

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1818617] [NEW] [amdgpu] screen corruption when using touchpad

2019-03-05 Thread Timo Aaltonen
Public bug reported:

An OEM system is suffering from screen corruption when the touchpad is
used. This would be fixed by backporting these commits from 4.18:

ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.

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

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

Title:
  [amdgpu] screen corruption when using touchpad

Status in linux-oem package in Ubuntu:
  New

Bug description:
  An OEM system is suffering from screen corruption when the touchpad is
  used. This would be fixed by backporting these commits from 4.18:

  ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw 
hand-over (v3)
  6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible.

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-03-04 Thread Timo Aaltonen
disco has 4.19.x

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

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-27 Thread Timo Aaltonen
Yes, in #43 you said that you tested 4.13.0-19.22 but didn't seem to
install the package with the drivers (linux-image-extra). If you do,
does it work like the live version did?

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

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

Bug description:
  The touchpad doesn't work unless the cursor is moved slowly.

  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  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+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: 

[Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-02-27 Thread Timo Aaltonen
you should've installed linux-image-extra for 4.13.0-19.22, testing
without it doesn't prove a thing

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

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

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

Bug description:
  The touchpad doesn't work unless the cursor is moved slowly.

  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  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+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  

[Kernel-packages] [Bug 1817848] [NEW] i915: Backport watermark fixes for gen9+

2019-02-27 Thread Timo Aaltonen
Public bug reported:

5.0 fixes screen flicker issues with new panel models and on hybrid
machines, and Intel has prepared a backport for 4.15 which we can use.
It consists of 50+ cherry-picked commits plus a handful of build fixes:

git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

It's a big change which needs to be tested properly on a wide array of
certified machines.

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

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Undecided
 Status: Confirmed

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

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

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

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

Title:
  i915: Backport watermark fixes for gen9+

Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  5.0 fixes screen flicker issues with new panel models and on hybrid
  machines, and Intel has prepared a backport for 4.15 which we can use.
  It consists of 50+ cherry-picked commits plus a handful of build
  fixes:

  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

  It's a big change which needs to be tested properly on a wide array of
  certified machines.

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

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


[Kernel-packages] [Bug 1815510] Re: System lag/stuttering, mouse movement and window drag choppiness with Vega 64

2019-02-15 Thread Timo Aaltonen
this needs to be filed upstream and preferably bisected to see why
that's happening

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

2019-02-15 Thread Timo Aaltonen
** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1034.39 -proposed tracker

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1814730] Re: linux-oem: -proposed tracker

2019-02-15 Thread Timo Aaltonen
** Summary changed:

- linux-oem: 4.15.0-1034.39 -proposed tracker
+ linux-oem:  -proposed tracker

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

2019-02-14 Thread Timo Aaltonen
** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1034.39 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen 
(tjaalton)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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


[Kernel-packages] [Bug 1815508] Re: Xorg freezes due to kernel hung task in the i915 driver

2019-02-13 Thread Timo Aaltonen
please try the latest mainline kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/

install the matching linux-modules pkg too

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xorg freezes due to kernel hung task in the i915 driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is present in 18.04 and is triggered by specific actions, in
  particular, paging through image galleries in Eye of Gnome. When the
  bug is triggered, Xorg freezes completely and goes into the D
  (uninterruptible sleep) state. The machine continues to respond to
  ping and ssh. When triggering a shutdown or reboot over ssh, the
  shutdown process continues normally until most userspace processes
  (including systemd-journald) have been stopped, but then hangs. The
  system can still be rebooted with the magic sysrq technique.

  Here's some dmesg output:

  [0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off

  ###
  # This error happens regularly and may be irrelevant:
  ###

  [  345.680936] [ cut here ]
  [  345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, 
pin_global=0
  [  345.680998] WARNING: CPU: 1 PID: 241 at 
/build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 
cancel_userptr+0xe8/0xf0 [i915]
  [  345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 
snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic 
xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel 
snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio 
videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp 
snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me 
mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
  [  345.681028]  scsi_transport_iscsi coretemp ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter 
ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt 
hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath 
linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt 
fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm 
pps_core ahci nvme_core libahci wmi video
  [  345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P   O 
4.15.0-45-generic #48-Ubuntu
  [  345.681059] Hardware name: System manufacturer System Product Name/PRIME 
B250M-C, BIOS 1402 11/16/2018
  [  345.681081] Workqueue: i915-userptr-release cancel_userptr [i915]
  [  345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915]
  [  345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282
  [  345.681098] RAX:  RBX: 8fb681b17600 RCX: 
0006
  [  345.681099] RDX: 0007 RSI: 0082 RDI: 
8fb6b6c96490
  [  345.681100] RBP: afc441edbe78 R08: 0001 R09: 
03c4
  [  345.681101] R10: e28d5018ef80 R11:  R12: 
8fb681b177a8
  [  345.681101] R13:  R14: 8fb698eba500 R15: 

  [  345.681102] FS:  () GS:8fb6b6c8() 
knlGS:
  [  345.681103] CS:  0010 DS:  ES:  CR0: 80050033
  [  345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 
003606e0
  [  345.681105] Call Trace:
  [  345.681110]  process_one_work+0x1de/0x410
  [  345.68]  worker_thread+0x32/0x410
  [  345.681113]  kthread+0x121/0x140
  [  345.681115]  ? process_one_work+0x410/0x410
  [  345.681116]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  345.681119]  ret_from_fork+0x35/0x40
  [  345.681120] Code: bf 46 ff ff eb c9 8b 93 c8 01 00 00 8b 8b a4 01 00 00 48 
c7 c7 40 44 7a c0 8b b3 9c 01 00 00 c6 05 b5 56 10 00 01 e8 e8 2a fc fa <0f> 0b 
eb bc 0f 1f 40 00 0f

[Kernel-packages] [Bug 1815510] Re: System lag/stuttering, mouse movement and window drag choppiness with Vega 64

2019-02-13 Thread Timo Aaltonen
You say just upgrading mesa would cause it on bionic too? It already got
18.2.2 from cosmic.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  System lag/stuttering, mouse movement and window drag choppiness with
  Vega 64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 18.10 and beyond, the desktop is quite laggy and choppy, to
  the point where moving windows around the screen appears to be a stop-
  motion at 5FPS or so. Mouse movement is choppy, animations are
  grindingly slow, and this overall slowness does seem to affect text
  input into GUI dialogs (missed keys, etc). However, performance is
  fine in TTY, even with more active programs like HTOP and full-screen
  text images like NCURSES looking stuff. This issue wasn't present in
  18.04(.1) but could be triggered by using a newer kernel or updating
  the MESA stack. I'm using a STRIX Vega 64 for my GPU and I've
  installed Ubuntu 19.04 and only run updates and installed inxi and lm-
  sensors so I can provide more data if possible. (EDIT: Would also like
  to note that CPU usage is pretty low, and there's nothing pinning the
  CPU or spiking it from time to time. I believe this is solely
  graphical, but I am *not* 100% certain at any rate.)

  System:
    Host: schyken-ryzen-horizon Kernel: 4.19.0-12-generic x86_64 bits: 64
    compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2
    Distro: Ubuntu 19.04 (Disco Dingo)
  Machine:
    Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
    serial:  UEFI: American Megatrends v: 4207 date: 12/07/2018
  CPU:
    Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
    rev: 2 L2 cache: 4096 KiB
    flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
    bogomips: 111784
    Speed: 1374 MHz min/max: 1550/3500 MHz Core speeds (MHz): 1: 1375 2: 1374
    3: 2779 4: 1700 5: 2793 6: 2625 7: 1270 8: 1270 9: 1375 10: 1375 11: 1375
    12: 1375 13: 1375 14: 1370 15: 1267 16: 1270
  Graphics:
    Device-1: AMD Vega 10 XT [Radeon RX Vega 64] vendor: ASUSTeK
    driver: amdgpu v: kernel bus ID: 0c:00.0
    Display: x11 server: X.Org 1.20.3 driver: amdgpu
    resolution: 2560x1440~60Hz
    OpenGL:
    renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-12-generic LLVM 7.0.1)
    v: 4.5 Mesa 18.3.2 direct render: Yes
  Audio:
    Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
    driver: snd_hda_intel v: kernel bus ID: 09:00.0
    Device-2: AMD driver: snd_hda_intel v: kernel bus ID: 0c:00.1
    Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus ID: 0e:00.3
    Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus ID: 3-3:3
    Device-5: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus ID: 1-1:2
    Sound Server: ALSA v: k4.19.0-12-generic
  Network:
    Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
    IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 
  Drives:
    Local Storage: total: 2.05 TiB used: 6.93 GiB (0.3%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB
    ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 22 C
    ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 19 C
    ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
    ID-5: /dev/sdd vendor: Western Digital model: WDS500G2B0A-00SM50
    size: 465.76 GiB temp: 21 C
  Partition:
    ID-1: / size: 91.29 GiB used: 6.92 GiB (7.6%) fs: ext4 dev: /dev/nvme0n1p3
  Sensors:
    System Temperatures: cpu: 27.2 C mobo: N/A gpu: amdgpu temp: 29 C
    Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 720
  Info:
    Processes: 373 Uptime: 2m Memory: 31.41 GiB used: 1.40 GiB (4.5%)
    Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2
    inxi: 3.0.32
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=66ecdf59-50f0-49c7-befa-d800622a2e25 ro quiet splash vt.handoff=1
  ProcVer

[Kernel-packages] [Bug 1815429] Re: Xorg crash

2019-02-12 Thread Timo Aaltonen
** Package changed: nvidia-graphics-drivers-410 (Ubuntu) => xfwm4
(Ubuntu)

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

Title:
  Xorg crash

Status in xfwm4 package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. setup a virtual machine with GPU pass-through to a nvidia Quadro
  card (nvidia only supports passthrough to Quadro cards). Nvidia also
  recommends that the passed-through card has its ROM disabled in VM
  configuration, i.e.  . Attached an example of such VM.

  2. install vanilla Xubuntu 18.04, do not enable auto-login

  3. install nvidia drivers, e.g.
    $ sudo add-apt-repository ppa:graphics-drivers/ppa
    $ sudo apt-get install nvidia-driver-410

  4. reboot (the screen may be black until the greeter appears)

  5. login

  6. lock the screen back to the greeter
    $ light-locker-command --lock

  Now you have black screen and unresponsive keyboard, and also one more file 
in /var/crash . The only way to get to the greeter again is to run (from 
another session, e.g. ssh)
    $ sudo systemctl restart lightdm

  ... which will also kill all the sessions running under the login
  manger (including the one where we tried to lock the screen)

  I've found that this only happens with stock xfwm4 version 4.12 . If I
  upgrade xfwm4 to version 4.13 (from Mint) the screen lock works as
  expected, but this package is not in Ubuntu repo.

  So perhaps the problem is not with Xorg but with old xfwm4. I also
  tried other flavours of Ubuntu and IIRC also seen it in Lubuntu.

  At a stretch this could be called security vulnerability, because with
  this bug there is no way to lock the screen, hence users will always
  leave their session unlocked (or must log off)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 
CST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog:

  CompositorRunning: None
  Date: Mon Feb 11 09:14:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 410.78, 4.15.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM204GL [Quadro M5000] [10de:13f0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation GM204GL [Quadro M5000] [10de:1152]
  InstallationDate: Installed on 2019-02-10 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=16524009-5b46-4f13-918c-0dee6cce40fe ro console=tty0 
console=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1815429] Re: Xorg crash

2019-02-12 Thread Timo Aaltonen
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-410
(Ubuntu)

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

Title:
  Xorg crash

Status in nvidia-graphics-drivers-410 package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1. setup a virtual machine with GPU pass-through to a nvidia Quadro
  card (nvidia only supports passthrough to Quadro cards). Nvidia also
  recommends that the passed-through card has its ROM disabled in VM
  configuration, i.e.  . Attached an example of such VM.

  2. install vanilla Xubuntu 18.04, do not enable auto-login

  3. install nvidia drivers, e.g.
    $ sudo add-apt-repository ppa:graphics-drivers/ppa
    $ sudo apt-get install nvidia-driver-410

  4. reboot (the screen may be black until the greeter appears)

  5. login

  6. lock the screen back to the greeter
    $ light-locker-command --lock

  Now you have black screen and unresponsive keyboard, and also one more file 
in /var/crash . The only way to get to the greeter again is to run (from 
another session, e.g. ssh)
    $ sudo systemctl restart lightdm

  ... which will also kill all the sessions running under the login
  manger (including the one where we tried to lock the screen)

  I've found that this only happens with stock xfwm4 version 4.12 . If I
  upgrade xfwm4 to version 4.13 (from Mint) the screen lock works as
  expected, but this package is not in Ubuntu repo.

  So perhaps the problem is not with Xorg but with old xfwm4. I also
  tried other flavours of Ubuntu and IIRC also seen it in Lubuntu.

  At a stretch this could be called security vulnerability, because with
  this bug there is no way to lock the screen, hence users will always
  leave their session unlocked (or must log off)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:06:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.78  Sat Nov 10 22:09:04 
CST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog:

  CompositorRunning: None
  Date: Mon Feb 11 09:14:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 410.78, 4.15.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM204GL [Quadro M5000] [10de:13f0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation GM204GL [Quadro M5000] [10de:1152]
  InstallationDate: Installed on 2019-02-10 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=16524009-5b46-4f13-918c-0dee6cce40fe ro console=tty0 
console=ttyS0,115200n8
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Timo Aaltonen
4.15 is EOL upstream, but Canonical does pull patches from stable to the
distro kernel in 18.04, I'm not sure why these never got in.. probably
didn't apply cleanly.

anyway, I'll make sure they get applied eventually, but for now will
disable softpin from mesa so that 32bit 18.04.2 image will work on gen8+

closing again, thanks!

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Timo Aaltonen
one theory is that this is related to legacy bios boot

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Timo Aaltonen
this is caused by enabling softpin in mesa, which is supported in kernel
4.5 and up but is still somewhat buggy as seen here.. we need these
commits backported to the kernel:

9125963a9494253fa5a29cc1b4169885d2be7042 drm/i915: Mark up GTT sizes as u64
6fc4e48f9ed46e9adff236a0c350074aafa3b7fa drm/i915: Compare user's 64b GTT 
offset even on 32b

but since 18.04.2 is about to be released, it's best to revert enabling
softpin in mesa, and enable it again for 18.04.3.

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  New

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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


[Kernel-packages] [Bug 1814610] Re: new kernel 4.15.0-45-generic fails to load intel driver

2019-02-05 Thread Timo Aaltonen
could be, if you didn't have any other 4.15.0-NN kernel installed

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

Title:
  new kernel 4.15.0-45-generic fails to load intel driver

Status in linux package in Ubuntu:
  Invalid

Bug description:
  new kernel 4.15.0-45-generic fails to load intel driver. the display
  refresh is almost nonexistent.

  recreate bug:
  upgrade kernel from  4.15.0-43-generic to 4.15.0-44-generic 
  experience the bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663
  reboot with 4.15.0-43-generic and demove 4.15.0-44-generic 
  install 4.15.0-45-generic and reboot
  the intel driver seems to not load and the display experience is almost non 
usable.
  reverting to 4.15.0-43-generic solves the issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  4 20:52:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-01-04 (31 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 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 03GMP2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn03GMP2:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1814610] Re: new kernel 4.15.0-45-generic fails to load intel driver

2019-02-05 Thread Timo Aaltonen
the metapackage will pull it, in this case 'linux-image-generic'

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

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

Title:
  new kernel 4.15.0-45-generic fails to load intel driver

Status in linux package in Ubuntu:
  Invalid

Bug description:
  new kernel 4.15.0-45-generic fails to load intel driver. the display
  refresh is almost nonexistent.

  recreate bug:
  upgrade kernel from  4.15.0-43-generic to 4.15.0-44-generic 
  experience the bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663
  reboot with 4.15.0-43-generic and demove 4.15.0-44-generic 
  install 4.15.0-45-generic and reboot
  the intel driver seems to not load and the display experience is almost non 
usable.
  reverting to 4.15.0-43-generic solves the issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  4 20:52:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-01-04 (31 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 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 03GMP2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn03GMP2:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1814610] Re: new kernel 4.15.0-45-generic fails to load intel driver

2019-02-05 Thread Timo Aaltonen
do you have linux-modules-extra-4.15.0-45-generic installed?

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

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

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

Title:
  new kernel 4.15.0-45-generic fails to load intel driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  new kernel 4.15.0-45-generic fails to load intel driver. the display
  refresh is almost nonexistent.

  recreate bug:
  upgrade kernel from  4.15.0-43-generic to 4.15.0-44-generic 
  experience the bug 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663
  reboot with 4.15.0-43-generic and demove 4.15.0-44-generic 
  install 4.15.0-45-generic and reboot
  the intel driver seems to not load and the display experience is almost non 
usable.
  reverting to 4.15.0-43-generic solves the issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  4 20:52:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-01-04 (31 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 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 03GMP2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn03GMP2:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-05 Thread Timo Aaltonen
or pick

commit 5179749925933575a67f9d8f16d0cc204f98a29f
Author: Chris Wilson 
Date:   Tue Dec 4 14:15:16 2018 +

drm/i915: Allocate a common scratch page

from drm-intel-next, will be in 4.18.21

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-05 Thread Timo Aaltonen
revert this:

commit 06e562e7f515292ea7721475950f23554214adde
Author: Chris Wilson 
Date:   Mon Nov 5 09:43:05 2018 +

drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5

commit fb5bbae9b1333d44023713946fdd28db0cd85751 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/1814555

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


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

2019-02-01 Thread Timo Aaltonen
there is no separate modesetting driver anymore, it's folded in the
server

that said, the bug is most likely in the kernel

** Package changed: xserver-xorg-video-modesetting (Ubuntu) => xorg-
server (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/1813423

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

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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


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

2019-01-31 Thread Timo Aaltonen
bionic has 18.2.2 now

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

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

Title:
  VegaM support

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

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

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

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

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

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


  1   2   3   4   5   6   7   8   9   10   >