[Kernel-packages] [Bug 1878635] [NEW] Intel Titan Ridge TB3 USB Controller prevents system from suspending

2020-05-14 Thread Sebastian Heiden
Public bug reported:

The dmesg log states the following:
PM: Device :0f:00.0 failed to suspend async: error -110

When checking lspci this points to the following device:
0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller 
[Titan Ridge 2C 2018] (rev 06)
which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

I will still try suspending without a Thunderbolt 3 Dock attached.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  spyfly 2424 F pulseaudio
 /dev/snd/controlC3:  spyfly 2424 F pulseaudio
 /dev/snd/controlC1:  spyfly 2424 F pulseaudio
 /dev/snd/controlC2:  spyfly 2424 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 17:09:55 2020
HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
InstallationDate: Installed on 2018-09-06 (616 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-29-generic N/A
 linux-backports-modules-5.4.0-29-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.78
dmi.board.name: X570 Phantom Gaming-ITX/TB3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal

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

Title:
  Intel Titan Ridge TB3 USB Controller prevents system from suspending

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The dmesg log states the following:
  PM: Device :0f:00.0 failed to suspend async: error -110

  When checking lspci this points to the following device:
  0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

  I will still try suspending without a Thunderbolt 3 Dock attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spyfly 2424 F pulseaudio
   /dev/snd/controlC3:  spyfly 2424 F pulseaudio
   /dev/snd/controlC1:  spyfly 2424 F pulseaudio
   /dev/snd/controlC2:  spyfly 2424 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 17:09:55 2020
  HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
  InstallationDate: Installed on 2018-09-06 (616 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.7

[Kernel-packages] [Bug 1878635] Re: Intel Titan Ridge TB3 USB Controller prevents system from suspending

2020-05-17 Thread Sebastian Heiden
** Package changed: linux (Ubuntu) => powermgmt-base (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/1878635

Title:
  Intel Titan Ridge TB3 USB Controller prevents system from suspending

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  The dmesg log states the following:
  PM: Device :0f:00.0 failed to suspend async: error -110

  When checking lspci this points to the following device:
  0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB 
Controller [Titan Ridge 2C 2018] (rev 06)
  which is the integrated Thunderbolt 3 Controller of the ITX Motherboard.

  I will still try suspending without a Thunderbolt 3 Dock attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  spyfly 2424 F pulseaudio
   /dev/snd/controlC3:  spyfly 2424 F pulseaudio
   /dev/snd/controlC1:  spyfly 2424 F pulseaudio
   /dev/snd/controlC2:  spyfly 2424 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 17:09:55 2020
  HibernationDevice: RESUME=UUID=3b541ffc-65d1-41a6-87d4-11750893bae2
  InstallationDate: Installed on 2018-09-06 (616 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.78
  dmi.board.name: X570 Phantom Gaming-ITX/TB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.78:bd11/01/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1878635/+subscriptions

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


[Kernel-packages] [Bug 1607783] [NEW] Fans running full speed on skylake platform

2016-07-29 Thread Sebastian Heiden
Public bug reported:

The Fans on my ASUS GL502VT Laptop start spinning full speed after about
2 minutes after bootup in default mode. If I boot with nomodeset boot
parameter it seems not to happen. The Device is running the lastest BIOS
by ASUS.

Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
Ubuntu Version: 16.04.1 LTS

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709438/+files/lspci-vnvn.log

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  New

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS

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

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


[Kernel-packages] [Bug 1607783] Re: Fans running full speed on skylake platform

2016-07-29 Thread Sebastian Heiden
apport information

** Tags added: apport-collected xenial

** Description changed:

  The Fans on my ASUS GL502VT Laptop start spinning full speed after about
  2 minutes after bootup in default mode. If I boot with nomodeset boot
  parameter it seems not to happen. The Device is running the lastest BIOS
  by ASUS.
  
  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
+ CasperVersion: 1.376
+ DistroRelease: Ubuntu 16.04
+ LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
+ MachineType: ASUSTeK COMPUTER INC. GL502VT
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
+ ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-31-generic N/A
+  linux-backports-modules-4.4.0-31-generic  N/A
+  linux-firmware1.157.2
+ Tags:  xenial
+ Uname: Linux 4.4.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 06/14/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: GL502VT.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: GL502VT
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: GL502VT
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709452/+files/AlsaInfo.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1607783/+attachment/4709458/+files/Lspci.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1607783/+attachment/4709463/+files/RfKill.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709454/+files/CurrentDmesg.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1607783/+attachment/4709453/+files/CRDA.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709455/+files/IwConfig.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709456/+files/JournalErrors.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1607783/+attachment/4709460/+files/ProcCpuinfo.txt

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

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

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


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

2016-07-29 Thread Sebastian Heiden
apport information

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1607783] Re: Fans running full speed on skylake platform

2016-07-29 Thread Sebastian Heiden
As this is a brand new device I tried 16.04 LTS first where the bug was
persistent, same for 14.04. But the lastest upstream kernel fixed this.
Thanks for your help.

** Tags added: kernel-fixed-upstream

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

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1607783] Re: Fans running full speed on skylake platform

2016-09-02 Thread Sebastian Heiden
Maybe its a dedicated GPU Fan Controlled by the GPU? Try installing the
lastest Nvidia Drivers, use mainline 4.6 for that and the Nvidia Drivers
ppa.

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

Title:
  Fans running full speed on skylake platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Fans on my ASUS GL502VT Laptop start spinning full speed after
  about 2 minutes after bootup in default mode. If I boot with nomodeset
  boot parameter it seems not to happen. The Device is running the
  lastest BIOS by ASUS.

  Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
  Ubuntu Version: 16.04.1 LTS
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4839 F pulseaudio
  CasperVersion: 1.376
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: ASUSTeK COMPUTER INC. GL502VT
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet nomodeset splash ---
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VT.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VT.300:bd06/14/2016:svnASUSTeKCOMPUTERINC.:pnGL502VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL502VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2023-01-05 Thread Sebastian Heiden
It seems like there is no more force-probe required for oem-6.1, works
fine out-of-the-box now.

When is the 22.2 mesa from ppa:canonical-x/x-staging going to be
released, currently using the linux-oem-6.1 kernel together with the
23.0 mesa from the Intel Arc package sources.

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1994025] Re: Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

2023-01-05 Thread Sebastian Heiden
Seems like this issue was caused by nvidia driver remainders, which
caused an instant wake-up after suspend or hibernate.

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

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

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

Title:
  Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

Status in linux-oem-6.0 package in Ubuntu:
  Invalid

Bug description:
  The computer is unable to suspend or hibernate, when a DG2 graphics
  card is installed and in-use in the system.

  When attempting to suspend or hibernate the system will turn off its
  screens for a few seconds after which they will light up again.

  I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages
  from the canonical-x/x-staging ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04b 6.0.0.1005.5
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 12:07:27 2022
  InstallationDate: Installed on 2022-02-23 (242 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-oem-6.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

2021-09-27 Thread Sebastian Heiden
I also experienced this bug on Ubuntu 21.10 Beta during boot on a fresh
ZFS Install with Encryption.

The only way to boot into GNOME without crashing was booting through
recovery mode.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  &zp->z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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


[Kernel-packages] [Bug 1949793] [NEW] Thunderbolt 3 NIC driver is loaded too early and won't establish connection

2021-11-04 Thread Sebastian Heiden
Public bug reported:

I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).

The issue is that during boot it only detects the interface as 5 GBe, as seen 
in dmesg:
enp11s0: atlantic: link change old 0 new 5000

This prevents the interface from establishing a connection. With Ubuntu
21.04 and previous versions this issue didn't exist.

I found a couple workarounds for this problem:
1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the 
BIOS. This prevents the computer from suspending however, so this workaround 
isn't feasible.
2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 
GBe without issues as seen below:
atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1

>From the obervations above, I draw the conclusion that the module gets
loaded too early with Thunderbolt Security disabled and should happen at
a later point in time.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  spyfly 3576 F pulseaudio
 /dev/snd/pcmC2D0p:   spyfly 3576 F...m pulseaudio
 /dev/snd/controlC1:  spyfly 3576 F pulseaudio
 /dev/snd/controlC0:  spyfly 3576 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  4 15:47:34 2021
HibernationDevice: RESUME=none
InstallationDate: Installed on 2021-10-19 (15 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.20
dmi.board.name: X570 Phantom Gaming-ITX/TB3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug impish

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

Title:
  Thunderbolt 3 NIC driver is loaded too early and won't establish
  connection

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10
  GBase-T NIC (atlantic).

  The issue is that during boot it only detects the interface as 5 GBe, as seen 
in dmesg:
  enp11s0: atlantic: link change old 0 new 5000

  This prevents the interface from establishing a connection. With
  Ubuntu 21.04 and previous versions this issue didn't exist.

  I found a couple workarounds for this problem:
  1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the 
BIOS. This prevents the computer from suspending however, so this workaround 
isn't feasible.
  2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 
10 GBe without issues as seen below:
  atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1

  From the obervations above, I draw the conclusion that the module gets
  loaded too early with Thunderbolt Security disabled and should happen
  at a later point in time.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  spyfly 3576 F pulseaudi

[Kernel-packages] [Bug 1949790] [NEW] Thunderbolt 3 NIC driver is loaded too early and won't establish connection

2021-11-04 Thread Sebastian Heiden
Public bug reported:

I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).

The issue is that during boot it only detects the interface as 5 GBe, as seen 
in dmesg:
enp11s0: atlantic: link change old 0 new 5000

This prevents the interface from establishing a connection. With Ubuntu
21.04 and previous versions this issue didn't exist.

I found a couple workarounds for this problem:
1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the 
BIOS. This prevents the computer from suspending however, so this workaround 
isn't feasible.
2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 10 
GBe without issues as seen below:
atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1

>From the obervations above, I draw the conclusion that the module gets
loaded too early with Thunderbolt Security disabled and should happen at
a later point in time.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  spyfly 3576 F pulseaudio
 /dev/snd/pcmC2D0p:   spyfly 3576 F...m pulseaudio
 /dev/snd/controlC1:  spyfly 3576 F pulseaudio
 /dev/snd/controlC0:  spyfly 3576 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  4 15:47:34 2021
HibernationDevice: RESUME=none
InstallationDate: Installed on 2021-10-19 (15 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.20
dmi.board.name: X570 Phantom Gaming-ITX/TB3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug impish

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

Title:
  Thunderbolt 3 NIC driver is loaded too early and won't establish
  connection

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10
  GBase-T NIC (atlantic).

  The issue is that during boot it only detects the interface as 5 GBe, as seen 
in dmesg:
  enp11s0: atlantic: link change old 0 new 5000

  This prevents the interface from establishing a connection. With
  Ubuntu 21.04 and previous versions this issue didn't exist.

  I found a couple workarounds for this problem:
  1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the 
BIOS. This prevents the computer from suspending however, so this workaround 
isn't feasible.
  2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 
10 GBe without issues as seen below:
  atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1

  From the obervations above, I draw the conclusion that the module gets
  loaded too early with Thunderbolt Security disabled and should happen
  at a later point in time.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  spyfly 3576 F pulseaudi

[Kernel-packages] [Bug 1949793] Re: Thunderbolt 3 NIC driver is loaded too early and won't establish connection

2021-11-04 Thread Sebastian Heiden
*** This bug is a duplicate of bug 1949790 ***
https://bugs.launchpad.net/bugs/1949790

** This bug has been marked a duplicate of bug 1949790
   Thunderbolt 3 NIC driver is loaded too early and won't establish connection

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

Title:
  Thunderbolt 3 NIC driver is loaded too early and won't establish
  connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10
  GBase-T NIC (atlantic).

  The issue is that during boot it only detects the interface as 5 GBe, as seen 
in dmesg:
  enp11s0: atlantic: link change old 0 new 5000

  This prevents the interface from establishing a connection. With
  Ubuntu 21.04 and previous versions this issue didn't exist.

  I found a couple workarounds for this problem:
  1. Enable Thunderbolt Security (User Authorization or Secure Connect) in the 
BIOS. This prevents the computer from suspending however, so this workaround 
isn't feasible.
  2. Run sudo rmmod atlantic && modprobe atlantic and the NIC will connect at 
10 GBe without issues as seen below:
  atlantic :0b:00.0 enp11s0: atlantic: link change old 0 new 1

  From the obervations above, I draw the conclusion that the module gets
  loaded too early with Thunderbolt Security disabled and should happen
  at a later point in time.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  spyfly 3576 F pulseaudio
   /dev/snd/pcmC2D0p:   spyfly 3576 F...m pulseaudio
   /dev/snd/controlC1:  spyfly 3576 F pulseaudio
   /dev/snd/controlC0:  spyfly 3576 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  4 15:47:34 2021
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-10-19 (15 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_qbynho@/vmlinuz-5.13.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu_qbynho ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X570 Phantom Gaming-ITX/TB3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-05-09 Thread Sebastian Heiden
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the
S0ix option fixed the problem for me.

I've added the following option
"nvidia.NVreg_EnableS0ixPowerManagement=1" to
GRUB_CMDLINE_LINUX_DEFAULT.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-05-09 Thread Sebastian Heiden
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by
@vanvugt

You may wanna change the file path of the temporary file thought for
better performance.

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.l

[Kernel-packages] [Bug 1960460] Re: Fails to import ZFS rpool during boot

2022-02-10 Thread Sebastian Heiden
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: 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/1960460

Title:
  Fails to import ZFS rpool during boot

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
  from the installer

  The system ends up in busybox after entering the unlock key.

  Here is a part of the logs captured from the screen, the complete log
  can be found as an attachement:

  find: /dev/zvol/: No such file or directory 
  /init: line 971: dirname: not found
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary.

  Usage: basename FILE [SUFFIX]
  Strip directory path and SUFFIX from FILE 
  Please unlock disk keystore-:_

  Key load error: Failed to open key material file: No such file or
  directory

  Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: 
filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied 
Error: 1

  Failed to mount rpool/ROOT/ubuntu ui69ph on /root//.
  Manually mount the filesystem and exit.

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


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


[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-03-21 Thread Sebastian Heiden
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  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/gnome-shell/+bug/1876632/+subscriptions


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


[Kernel-packages] [Bug 1962162] [NEW] Suspend/Resume/Reboot fails with 5.15 Kernel

2022-02-24 Thread Sebastian Heiden
Public bug reported:

Suspend/Resume and don't seem to work with the shipped 5.15 Kernel.

When rebooting or shutting down the system gets stuck at "Reached
Target: System Poweroff" or "Reboot".

Installing the mainline kernel 5.16.11 fixes this issue and the system
is able to properly shutdown/reboot and suspend.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-18-generic 5.15.0-18.18
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Feb 24 12:53:52 2022
HibernationDevice: RESUME=none
InstallationDate: Installed on 2022-02-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
MachineType: Micro-Star International Co., Ltd. MS-7D29
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-18-generic N/A
 linux-backports-modules-5.15.0-18-generic  N/A
 linux-firmware 20220217.git6342082c-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.24
dmi.board.asset.tag: Default string
dmi.board.name: MEG Z690I UNIFY (MS-7D29)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.24:bd01/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D29:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690IUNIFY(MS-7D29):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D29
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug jammy

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

Title:
  Suspend/Resume/Reboot fails with 5.15 Kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Suspend/Resume and don't seem to work with the shipped 5.15 Kernel.

  When rebooting or shutting down the system gets stuck at "Reached
  Target: System Poweroff" or "Reboot".

  Installing the mainline kernel 5.16.11 fixes this issue and the system
  is able to properly shutdown/reboot and suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Feb 24 12:53:52 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2022-02-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  MachineType: Micro-Star International Co., Ltd. MS-7D29
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_m9rbzq@/vmlinuz-5.15.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_m9rbzq ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.24
  dmi.board.asset.tag: Default string
  dmi.board.name: MEG Z690I UNIFY (MS-7D29)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.24:bd01/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D29:

[Kernel-packages] [Bug 1964440] Re: 5.15.0-22: No console displayed on EFI systems

2022-03-13 Thread Sebastian Heiden
Was able to reproduce this issue on two of my machines aswell. Both were
installed in EFI Mode.

Booting the older 5.15.0-18 kernel or 5.16 mainline kernels work around
this issue.

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

Title:
  5.15.0-22: No console displayed on EFI systems

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  DISCLAIMER:
  This is my second-ever bug report. Apologies in advance for any missing or 
inaccurate info. I am willing to troubleshoot and supply more/better info as 
needed.

  PROBLEM DESCRIPTION:
  After upgrading the kernel on my Ubuntu 22.04 Server test system from 
5.15.0-18 to 5.15.0-22, I see absolutely no console output on my display past 
the grub menu.

  I can give the system a few seconds to finish booting, log in blindly and 
watch the activity LEDs on e.g. the network interface as i run a ping or 
similar.
  I can also log in remotely via SSH, and/or use a serial console. So the 
system definitely does boot. But my actual display/screen shows no console 
output.

  ENVIRONMENT:

  (Output gathered via SSH while display was showing no output)

  testuser@testserver:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  testuser@testserver:~$ uname -a
  Linux testserver 5.15.0-22-generic #22-Ubuntu SMP Tue Feb 8 10:16:30 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

  This was initially discovered on an Ubuntu Server VM running in EFI mode on 
VirtualBox 6.1.32.
  System was installed with the daily 'jammy-live-server-amd64.iso' image from 
2022-03-07, fully upgraded as of 2022-03-10.
  Switching Graphics Controller in Virtualbox does not help, nor does 
'nomodeset' or 'noacpi'.
  I am able to reproduce the issue on real hardware and with different physical 
graphics cards.

  Similar symptoms can also be observed in Ubuntu Desktop (still using EFI) by 
attempting to switch to tty with CTRL + ALT + F[3-6], or by taking note of the 
missing plymouth screen during boot.
  Systems installed/booted in legacy BIOS mode (both Server and Desktop) do not 
appear to be affected.

  I have tried reinstalling on both virtual and hardware platforms, with
  same result before and after upgrading the kernel.

  HOW TO REPRODUCE - Ubuntu Server:
  - Boot existing Ubuntu Server EFI installation with 5.15.0-18 and observe 
console output
  - Set GRUB_TIMEOUT_STYLE=menu and GRUB_TIMEOUT=10 in /etc/default/grub (to 
enable rollback)
  - Run update-grub
  - Run sudo apt full-upgrade and watch linux version 5.15.0-22 get installed
  - Reboot and observe your display (no console output will be shown after grub)

  HOW TO REPRODUCE - Ubuntu Desktop:
  - Download Ubuntu 22.04 Desktop daily ISO
  - Write ISO to USB
  - Boot from USB in EFI mode
  - Install system
  - Run sudo apt full-upgrade and upgrade linux* to kernel 5.15.0-22
  - Reboot and observe missing plymouth screen during boot
  - Wait for graphical login screen to appear
  - Press CTRL + ALT + F[3-6] (screen will go black and/or freeze)
  - Press CTRL + ALT + F1 (screen will unfreeze and/or return to gdm greeter)

  WORKAROUNDS:
  If you still have 5.15.0-18 or earlier installed, select it in Grub.
  and/or install mainline kernel 5.16.11+ (for testing only - will not work if 
you have Secure Boot enabled).
  Alternatively, re-install/convert/boot your system to boot in legacy BIOS 
mode.

  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.15.0-22-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220307)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=8fe5

[Kernel-packages] [Bug 1964305] Re: [nvidia] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)

2022-03-13 Thread Sebastian Heiden
Was able to reproduce this bug on two of my machines aswell. Both were
using Nvidia 3000 Series graphics. Booting the 5.15.0-18 Kernel or 5.16
Mainline Kernels didn't have this issue.

Seems like only 5.15.0-22 is affected by this bug.

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

Title:
  [nvidia] Missing VTs in kernel 5.15.0-22-generic (but
  5.15.0-18-generic works)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works).

  Steps to reproduce:

  1. Boot Ubuntu.
  2. Press Ctrl+Alt+F4.

  Expected: VT to be displayed
  Observed: Monitor turns off.

  Notes:
   * This failure only happens in 5.15.0-22-generic. Kernel version 
5.15.0-18-generic works fine.
   * I am currently using the nvidia-470 driver in case that's relevant.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Wed Mar  9 14:33:12 2022
  InstallationDate: Installed on 2021-11-05 (123 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  MachineType: Intel(R) Client Systems NUC9i7QNX
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QXCFL579.0034.2019.1125.1436
  dmi.board.name: NUC9i7QNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K49245-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 24.33
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
  dmi.product.family: QN
  dmi.product.name: NUC9i7QNX
  dmi.product.sku: BXNUC9i7QNX
  dmi.product.version: K49244-403
  dmi.sys.vendor: Intel(R) Client Systems

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


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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-11-19 Thread Sebastian Heiden
The new firmware package works fine with the 6.0 kernel, it loads the GuC and 
HuC Firmware, as seen below:
[4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware 
i915/dg2_dmc_ver2_06.bin (v2.6)
[4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin 
version 70.

I presume the firmware updates are a preparation for the i915/drm
backports to the 6.0-oem kernel?

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-11-21 Thread Sebastian Heiden
Is this not going to happen?
> kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip

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

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
  firmare: updates to i915 DMC, GuC

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-10-11 Thread Sebastian Heiden
Are there any plans for providing an i915 DKMS Module with DG2 Support
for oem-5.17?

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1992532] [NEW] Enable DG2 graphics support

2022-10-11 Thread Sebastian Heiden
Public bug reported:

DG2 graphics support should be enabled by default, dmesg outputs the
following:

i915 :67:00.0: Your graphics device 56a5 is not properly supported by the 
driver in this
   kernel version. To force driver probe anyway, use 
i915.force_probe=56a5
   module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 
configuration option,
   or (recommended) check for kernel updates.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-oem-22.04b 6.0.0.1005.5
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 01:29:02 2022
InstallationDate: Installed on 2022-10-11 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-oem-6.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy package-from-proposed

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

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

Title:
  Enable DG2 graphics support

Status in linux-oem-6.0 package in Ubuntu:
  New

Bug description:
  DG2 graphics support should be enabled by default, dmesg outputs the
  following:

  i915 :67:00.0: Your graphics device 56a5 is not properly supported by the 
driver in this
 kernel version. To force driver probe anyway, use 
i915.force_probe=56a5
 module parameter or CONFIG_DRM_I915_FORCE_PROBE=56a5 
configuration option,
 or (recommended) check for kernel updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04b 6.0.0.1005.5
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 01:29:02 2022
  InstallationDate: Installed on 2022-10-11 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-oem-6.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1992667] [NEW] Application windows invisible (on DG2 graphics)

2022-10-12 Thread Sebastian Heiden
Public bug reported:

When using GNOME Shell with Wayland, all application windows become
invisible from time to time. This usually happens right after starting
GNOME Shell for the first time or after having a VRAM intensive
application open, such as a game.

I have installed the latest linux-oem-6.0 kernel and manually enabled
support for DG2 graphics by passing the i915.force_probe parameter with
the PCIe ID of the graphics card.

I have attached a screenshot of the described behavior below.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 17:23:40 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-10-11 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot of the described bug"
   
https://bugs.launchpad.net/bugs/1992667/+attachment/5623541/+files/gnome_shell_invisible_windows.png

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

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

Title:
  Application windows invisible (on DG2 graphics)

Status in gnome-shell package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-10-12 Thread Sebastian Heiden
Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.

It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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


[Kernel-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)

2022-10-13 Thread Sebastian Heiden
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've
attached the requested lspci output for the A770.

Ubuntu 22.04 has already received a mesa update with backported patches
for DG2 support:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712

I haven't tried 22.10 yet, but I will do so in the coming days.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+attachment/5623860/+files/lspci.txt

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

Title:
  Application windows invisible (on DG2 graphics)

Status in linux-oem-6.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1992667] Re: Application windows invisible (on DG2 graphics)

2022-10-23 Thread Sebastian Heiden
Hi Timo,

Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages
from the intel repository (https://dgpu-docs.intel.com/installation-
guides/ubuntu/ubuntu-jammy-arc.html) works as well.

Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04?

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

Title:
  Application windows invisible (on DG2 graphics)

Status in linux-oem-6.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 source package in Jammy:
  New
Status in mesa source package in Jammy:
  New

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1994025] [NEW] Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

2022-10-24 Thread Sebastian Heiden
Public bug reported:

The computer is unable to suspend or hibernate, when a DG2 graphics card
is installed and in-use in the system.

When attempting to suspend or hibernate the system will turn off its
screens for a few seconds after which they will light up again.

I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages
from the canonical-x/x-staging ppa.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-oem-22.04b 6.0.0.1005.5
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 24 12:07:27 2022
InstallationDate: Installed on 2022-02-23 (242 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-oem-6.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

Title:
  Suspend or hibernate fails when using Arc Alchemist (DG2) graphics

Status in linux-oem-6.0 package in Ubuntu:
  New

Bug description:
  The computer is unable to suspend or hibernate, when a DG2 graphics
  card is installed and in-use in the system.

  When attempting to suspend or hibernate the system will turn off its
  screens for a few seconds after which they will light up again.

  I am using the latest linux-oem-6.0 kernel and the mesa 22.2 packages
  from the canonical-x/x-staging ppa.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04b 6.0.0.1005.5
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 12:07:27 2022
  InstallationDate: Installed on 2022-02-23 (242 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-oem-6.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Kernel-packages] [Bug 1994157] [NEW] Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem Kernel

2022-10-25 Thread Sebastian Heiden
Private bug reported:

When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium
won't open anymore.

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

** Information type changed from Public to Private

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

Title:
  Chromium and Firefox snap won't launch with Linux 6.0.0-1006-oem
  Kernel

Status in linux-oem-6.0 package in Ubuntu:
  Invalid

Bug description:
  When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and
  Chromium won't open anymore.

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


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


[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

2021-10-07 Thread Sebastian Heiden
The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which
prevents the system from booting in the first place.

Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to
version 2.0.6, fixed the issue for me.

I hope that the release image of Ubuntu 21.10 will ship with zfs-
kmod-2.0.6 in the kernel by default.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  &zp->z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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