from:"h"

I ran "apport-collect 2009226" while booted to 5.19.0-32, not while
booted to 5.19.0-35 because X/Wayland doesn't start in 5.19.0-35.  If
apport-collect will run in a terminal window then I can boot to
5.19.0-35 and run apport-collect if needed/helpful.

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651504/+files/acpidump.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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651498/+files/ProcCpuinfoMinimal.txt

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2009226/+attachment/5651496/+files/PaInfo.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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651495/+files/Lsusb-v.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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651494/+files/Lsusb-t.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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2009226/+attachment/5651493/+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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651492/+files/Lspci-vt.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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

apport information

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: EP45-UD3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: EP45-UD3P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen

apport information

** Tags added: apport-collected jammy wayland-session

** Description changed:

- I updated software this morning and on reboot ubuntu kernel 5.19.0-35
- gives black screen.  It appears to be an issue with graphics as I can
- access a console and login. I am able boot and run normally with
- 5.19.0-32-generic.  I am using nvidia drivers.
+ I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
+  /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
+  /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
+  /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-11-12 (111 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
+ IwConfig:
+  lono wireless extensions.
+  
+  enp5s0no wireless extensions.
+  
+  enp6s0no wireless extensions.
+ MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-32-generic N/A
+  linux-backports-modules-5.19.0-32-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.10
+ RfKill:
+  
+ Tags:  jammy wayland-session
+ Uname: Linux 5.19.0-32-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/23/2009
+ dmi.bios.vendor: Award Software International, Inc.
+ dmi.bios.version: FD
+ dmi.board.name: EP45-UD3P
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
+ dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
+ dmi.product.name: EP45-UD3P
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2009226/+attachment/5651489/+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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives 
black screen.  It appears to be an issue with graphics as I can access a 
console and login. I am able boot and run normally with 5.19.0-32-generic.  I 
am using nvidia drivers.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC1:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC0:  ehwelbon  200265 F pulseaudio
   /dev/snd/controlC2:  ehwelbon  200265 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-12 (111 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   
  Tags:

[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen

2023-03-03 Thread Edward H. Welbon

** Description changed:

- I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
- It appears to be an issue with graphics as I can access a console and
- login. I am able boot with 5.19.0-32-generic.  I am using nvidia
- drivers.
+ I updated software this morning and on reboot ubuntu kernel 5.19.0-35
+ gives black screen.  It appears to be an issue with graphics as I can
+ access a console and login. I am able boot and run normally with
+ 5.19.0-32-generic.  I am using nvidia drivers.

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I updated software this morning and on reboot ubuntu kernel 5.19.0-35
  gives black screen.  It appears to be an issue with graphics as I can
  access a console and login. I am able boot and run normally with
  5.19.0-32-generic.  I am using nvidia drivers.

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


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

[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen

2023-03-03 Thread Edward H. Welbon

I am not running in problematic update but I have attached sudo lspci
-vnvn > lspci-vnvn.log


** Attachment added: "output of sudo lspci -vnvn > lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+attachment/5651446/+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/2009226

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  New

Bug description:
  I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
  It appears to be an issue with graphics as I can access a console and
  login. I am able boot with 5.19.0-32-generic.  I am using nvidia
  drivers.

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


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

[Kernel-packages] [Bug 2009226] [NEW] updating to ubuntu kernel 5.19.0-35 gives black screen

2023-03-03 Thread Edward H. Welbon

Public bug reported:

I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
It appears to be an issue with graphics as I can access a console and
login. I am able boot with 5.19.0-32-generic.  I am using nvidia
drivers.

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

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

Title:
  updating to ubuntu kernel 5.19.0-35 gives black screen

Status in linux package in Ubuntu:
  New

Bug description:
  I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
  It appears to be an issue with graphics as I can access a console and
  login. I am able boot with 5.19.0-32-generic.  I am using nvidia
  drivers.

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


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

Re: [Kernel-packages] [Bug 1978416] Re: External USB webcam is not working

2023-01-26 Thread Darshan H

Update: It was the issue with the webcam firmware, I contacted Hikvision
and they were not able to fix it. I returned it and bought different webcam
from Logitech.

On Thu, 26 Jan, 2023, 1:40 PM Isuru, <1978...@bugs.launchpad.net> wrote:

> This happened to me on 18.04 and 20.04 both. I am seeing similar logs to
> the previous comments and one major problem is that the laptop would not
> even boot up if the webcam is plugged in. It gets stuck at boot time and
> until I remove the webcam, it keeps stuck in the same black screen.
>
> If I keep it plugged and it doesn't respond, the entire system gets
> stuck until I remove it.
>
> I am using the a Hikvision U12 Full HD 1080P USB Webcam
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1978416
>
> Title:
>   External USB webcam is not working
>
> Status in linux-signed-hwe-5.13 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked
>   for once after trying multiple times, then it stopped working again.
>   It worked when I connected it to a USB 2.0 port and now it's not
>   working there as well. The device is showing up in lsbsb and dmseg,
>   but not showing in "v4l2-ctl --list-devices".
>
>   error in dmesg:
>   [10856.771936] usb 3-4: new high-speed USB device number 13 using
> xhci_hcd
>   [10856.929763] usb 3-4: New USB device found, idVendor=2bdf,
> idProduct=0280, bcdDevice=50.00
>   [10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
>   [10856.929776] usb 3-4: Product: 1080P Web Camera
>   [10856.929779] usb 3-4: Manufacturer: SN0002
>   [10856.929781] usb 3-4: SerialNumber: SN0002
>   [10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera
> (2bdf:0280)
>   [10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control
> : -32 (exp. 26).
>   [10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
>   ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
>   Uname: Linux 5.13.0-48-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.11-0ubuntu27.24
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jun 12 23:40:45 2022
>   InstallationDate: Installed on 2020-09-07 (643 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   SourcePackage: linux-signed-hwe-5.13
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978416/+subscriptions
>
>

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

Title:
  External USB webcam is not working

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked
  for once after trying multiple times, then it stopped working again.
  It worked when I connected it to a USB 2.0 port and now it's not
  working there as well. The device is showing up in lsbsb and dmseg,
  but not showing in "v4l2-ctl --list-devices".

  error in dmesg:
  [10856.771936] usb 3-4: new high-speed USB device number 13 using xhci_hcd
  [10856.929763] usb 3-4: New USB device found, idVendor=2bdf, idProduct=0280, 
bcdDevice=50.00
  [10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [10856.929776] usb 3-4: Product: 1080P Web Camera
  [10856.929779] usb 3-4: Manufacturer: SN0002
  [10856.929781] usb 3-4: SerialNumber: SN0002
  [10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera (2bdf:0280)
  [10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control : 
-32 (exp. 26).
  [10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 12 23:40:45 2022
  InstallationDate: Installed on 2020-09-07 (643 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978416/+subscriptions


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

[Kernel-packages] [Bug 1995238] Re: snaps randomly crash after some time

2022-11-02 Thread Donald H Locker

snapcraft bug report (thank you, Robin) updated to point to squashfs fix (not 
yet in distribution?) documented here:
 https://lore.kernel.org/lkml/20221020223616.7571-1-phil...@squashfs.org.uk/

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

Title:
  snaps randomly crash after some time

Status in snapd:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-
  record-linux-6-0/32160.

  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

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


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

[Kernel-packages] [Bug 1990997] [NEW] en_ZA locale not correct in applications

2022-09-27 Thread Mark H

Public bug reported:

In all Ubuntu based distributions I have found that in applications such
as LibreOffice Calc where I need to see formats applicable to my locale
en_ZA (South Africa) the decimal place is denoted by , in the
application even though the file /usr/share/i18n/locales/en_ZA is
correct in specifying the decimal place as denoted by a .

This is the same for monetary values where it is showing , in
applications instead of the . as specified in the locale file. The comma
was deprecated in South Africa in the 1990s and the generally accepted
decimal is .

This makes it extremely difficult to transfer Windows Excel files that
have decimal points to a Linux distro that strictly enforces recognising
a decimal with a comma and hence renders the Windows Excel file useless
in Linux.

The Windows feature of customising locales in terms of date, time,
decimal place and digit grouping within the GUI is sorely missing from
all desktops in Linux and so this cannot be fixed by the end-user.

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


** Tags: africa currency decimal locale south za

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

Title:
  en_ZA locale not correct in applications

Status in linux package in Ubuntu:
  New

Bug description:
  In all Ubuntu based distributions I have found that in applications
  such as LibreOffice Calc where I need to see formats applicable to my
  locale en_ZA (South Africa) the decimal place is denoted by , in the
  application even though the file /usr/share/i18n/locales/en_ZA is
  correct in specifying the decimal place as denoted by a .

  This is the same for monetary values where it is showing , in
  applications instead of the . as specified in the locale file. The
  comma was deprecated in South Africa in the 1990s and the generally
  accepted decimal is .

  This makes it extremely difficult to transfer Windows Excel files that
  have decimal points to a Linux distro that strictly enforces
  recognising a decimal with a comma and hence renders the Windows Excel
  file useless in Linux.

  The Windows feature of customising locales in terms of date, time,
  decimal place and digit grouping within the GUI is sorely missing from
  all desktops in Linux and so this cannot be fixed by the end-user.

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


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

[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade

2022-09-02 Thread Sascha H.

I also have Performance issues, so i managed to get pattern on my machine.
I have a Rycen 5, 32GB Ram and a Nvidia card.

i had 20.04 it was fine, then i did a fresh install for 22.04.
The first 2 days or so i had no trouble, yes it runs a bit laggy but i was fine 
with it, then i played a game. It was horrible, after closing my browser the 
game runs fine.
So i startet to search for something, maybe my RAM runs full? Check no it hit 
17GB out of 32, so at exactly 17GB it starts to go crazy, CPU usage is ok, some 
go to like 60% max but it laggs all over the place. I had no CPU usage spike 
over say 70% on working and/or gaming.
I dont know how to see my GPU usage.

I also can rebuild the youtube Tab lag, after like 12 GB of RAM usage it goes 
slower, but not much.
I stoped this test at 20GB, i hat a max CPU usage of 84% and ~78% on the rest 
of the cores.
So, only on my web browser its fine to go to 12GB, at 17GB ist bad at 20GB its 
the same as 17GB, But a playing a game and the web browser at the same time at 
17GB its realy bad.
I dont know maybe someone can work with this informations.

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

Title:
  massive performance issues since 22.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  After upgrading to 22.04 i had to fight with massive performance issues.

  Browsers appeared to hang every other minute, youtube videos being
  laggy and hang in between, applications in a virtualbox VM where slow
  and also hanging every other minute to a level of not being useable.
  On a pretty recent and powerful system just 2 years old.

  I noticed CPU jumps in top, but also somehow thought it could be a graphics 
issue so invested some time installing nvidia drivers properly.
  Also I wondered if it might be the lowlatency kernel I normally use because I 
do audio stuff, and switched to generic. But nothing helped.

  ThenI had the idea it could be a kernel/scheduler issue because the
  system wasn't always slow, but it appeared certain things kept hanging
  when other processed had a lot of cpu for a few seconds.

  So I got a recent mainline kernel, configured it with my last running
  config from 21.10 before the update, made the debs and installed them,
  and now can tell that a mainline kernel 5.17.7 with all the dkms
  modules that i had before which got compiled automatically at
  installation brings back a "normal" performance.

  I can browse the web, run multiple youtube vids at once, even in
  another browser, have thunderbird running, and a virtualbox machine
  open with another browser for some web app testing and everything runs
  fine and smooth, no lagging.

  Not sure yet what the real reason is - either the kernel version, or a
  patch in the ubuntu version, or the 22.04 kernel config so far, or
  some configuration made in 21.10 that isn't good with 22.04 and it's
  kernel anymore.

  I will go ahead tomorrow and see if I can build a vanilla kernel with
  the config from the ubuntu 22.04 kernel and "make oldconfig", then I
  will be able to tell if only the config is making the difference.

  Please let me know of there is anything I should test to further
  analyze this issue, or any ideas I can try to solve it without having
  to run a mainline manually installed kernel.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.30.33
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  henning6198 F pulseaudio
   /dev/snd/controlC1:  henning6198 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 23:02:38 2022
  InstallationDate: Installed on 2020-04-12 (761 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QV00CEGE
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=/dev/mapper/vgubuntu-root ro
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago)
  dmi.bios.date: 12/06/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET55W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00CEGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23

[Kernel-packages] [Bug 1987040] Re: [i915] Max resolution for FullHD monitor is 1024x768

2022-08-19 Thread Jesus H

Hi Daniel, well first of all I sent this bug because I saw the option and I 
just checked.
Thougth it was something automatic and anyone would reply, so instead thanks to 
you!

After you mentioned, I just realized my laptop has an miniDP connector.
My monitor doesnt have DisplayPort, so I used an VGA<->miniDP adapter, a friend 
had a unit of exactly this item https://www.ebay.es/itm/353392052156
It didnt work. My laptop screen went black and nothing in the monitor (made 
sure to select VGA input).
(Im not sure if your concern about VGA still affects here, as the output port 
is miniDP, but still is VGA in the other end)

I just made sure that I can connect through VGA well and with FullHD, in a 
Windows 10 partition in this same laptop, so just discarded the option the VGA 
port itself is bad.
I dont understand why Linux and graphics is so hard!

Thanks a lot for your time, highly appreciated.

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

Title:
  [i915] Max resolution for FullHD monitor is 1024x768

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have 1 external monitor, and the max resolution for this FullHD
  monitor which I can configure is 1024x768

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 19 08:40:15 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2022-06-04 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 2349AV6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=b8deb0ab-b1f3-469e-85fe-3cf4a56dc624 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2016
  dmi.bios.release: 2.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB0WW (2.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349AV6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: BB70374050
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:br2.70:efr1.13:svnLENOVO:pn2349AV6:pvrThinkPadT430:rvnLENOVO:rn2349AV6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2349:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349AV6
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1978416] [NEW] External USB webcam is not working

2022-06-12 Thread Darshan H

Public bug reported:

Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked for
once after trying multiple times, then it stopped working again. It
worked when I connected it to a USB 2.0 port and now it's not working
there as well. The device is showing up in lsbsb and dmseg, but not
showing in "v4l2-ctl --list-devices".

error in dmesg:
[10856.771936] usb 3-4: new high-speed USB device number 13 using xhci_hcd
[10856.929763] usb 3-4: New USB device found, idVendor=2bdf, idProduct=0280, 
bcdDevice=50.00
[10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10856.929776] usb 3-4: Product: 1080P Web Camera
[10856.929779] usb 3-4: Manufacturer: SN0002
[10856.929781] usb 3-4: SerialNumber: SN0002
[10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera (2bdf:0280)
[10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control : -32 
(exp. 26).
[10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 12 23:40:45 2022
InstallationDate: Installed on 2020-09-07 (643 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  External USB webcam is not working

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked
  for once after trying multiple times, then it stopped working again.
  It worked when I connected it to a USB 2.0 port and now it's not
  working there as well. The device is showing up in lsbsb and dmseg,
  but not showing in "v4l2-ctl --list-devices".

  error in dmesg:
  [10856.771936] usb 3-4: new high-speed USB device number 13 using xhci_hcd
  [10856.929763] usb 3-4: New USB device found, idVendor=2bdf, idProduct=0280, 
bcdDevice=50.00
  [10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [10856.929776] usb 3-4: Product: 1080P Web Camera
  [10856.929779] usb 3-4: Manufacturer: SN0002
  [10856.929781] usb 3-4: SerialNumber: SN0002
  [10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera (2bdf:0280)
  [10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control : 
-32 (exp. 26).
  [10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 12 23:40:45 2022
  InstallationDate: Installed on 2020-09-07 (643 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978416/+subscriptions


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

[Kernel-packages] [Bug 1960159] Re: 5.13 amdgpu, random pixel screen

2022-02-09 Thread Markus H

Hi Juerg,
Installing the new firmware fixes it.Got some error messages but now I am on
5-13.0-28
Thank you for the support.

** Attachment added: "Screenshot_2022-02-09_22-51-01.png"

https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960159/+attachment/5560088/+files/Screenshot_2022-02-09_22-51-01.png

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

Title:
5.13 amdgpu, random pixel screen

Status in linux-hwe-5.13 package in Ubuntu:
New

Bug description:
Hi, I have a Laptop with a Ryzen 5500U, running Linux Mint 20.3. To
make use of the graphics driver, I update the kernel from 5.4 to 5.13.
The computer is booting up, the LM splash screen apprears and then the
screen gets funky with a random assignment of pixels. It seems each
pixel gets a random assigned color (white, red, blue, green?, black).
The pixels change color roughly every 200-500 ms. This happens with
5.13.0-28 and 5.13.0-23. The laptop is not responding to anything.

Using 5.11.22 works without any flaws. AMD gpu drivers are installed
correctly.

Mandatory information 1st:

This one is running:
Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22

Description: Linux Mint 20.3
Release: 20.3

description: Notebook
product: 82LM (LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05)
vendor: LENOVO
version: IdeaPad 5 14ALC05
serial: MP1X
width: 64 bits

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

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

[Kernel-packages] [Bug 1960011] Re: Laptop internal display random noise, external monitor works. Rolling back to 5.11.0-46-generic works, kernels 5.13.0-27-generic and linux-image-5.13.0-28-generic d

2022-02-09 Thread h-tech

That solved the issue i am currently running 5.13.0-28-generic with no
random noise on the laptop screen.


Regarding the package i installed, should i uninstall it so it doesn't cause 
issues in the future or will a future update replace it? (I will surely forget 
about this custom install in a month)


Do i mark this as resolved or is there some other procedure?

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

Title:
  Laptop internal display random noise, external monitor works. Rolling
  back to 5.11.0-46-generic works,  kernels 5.13.0-27-generic and linux-
  image-5.13.0-28-generic does not work

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  Issue: Laptop internal display random noise, external monitor works. 
  Rolling back to 5.11.0-46-generic works

  Both kernels below causes he same issue
  5.13.0-27-generic
  5.13.0-28-generic


  First i thought it was due to installing CUDA. But removing CUDA and NVIDIA 
drivers didn't work.
  Only switching kernels did.


  I used the "ubuntu-bug linux" command to report this so i assume all
  necessary files are included automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  4 11:38:31 2022
  InstallationDate: Installed on 2021-07-22 (196 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960011/+subscriptions


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

[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports

2022-01-24 Thread Alan H

I'm seeing something that seems similar, but with 1.187.25, i think.
Is this related? https://ubuntuforums.org/showthread.php?t=2471244

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

Title:
  linux-firmware 1.187.24 may crash USB ports

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  5.4.0-92-generic

  linux-firmware:
Instalados: 1.187.24
Candidato:  1.187.24
Tabla de versión:
   *** 1.187.24 500
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.187 500
  500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages

  linux-firmware 1.187.24 upgrade disabled all mainboard USB ports.
  USB keyboard and mouse stopped working on the next reboot after upgrade.
  I disconnected an USB bluetooth key from a back USB port, rebooted, and 
everything restored to normality.
  My personal conclusion: there is a bug in the bluetooth firmware update that 
may cause a general USB crash when an USB bluetooth key is connected.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alvaro 2225 F pulseaudio
   /dev/snd/controlC0:  alvaro 2225 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a
  InstallationDate: Installed on 2014-10-25 (2634 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B365M H
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 1.187.24
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic 
root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-92-generic N/A
   linux-backports-modules-5.4.0-92-generic  N/A
   linux-firmware1.187.24
  RfKill:
   2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago)
  UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo 
video
  _MarkForUpload: True
  dmi.bios.date: 08/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4b
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B365M H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1945367] Re: [nvidia] Graphics freeze

2021-11-22 Thread j l h

End off this bug !!!
I have installed nvidia-driver-470 tested and updated by ubuntu, and the bug 
disappear !!
I note that the version of the nvidia driver passed from 470.62 to 470.82, is 
it the reason why it works now ? i don't know.
Thanks to the developer who have done the necessary :-)
Have a good day.

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

Title:
  [nvidia] Graphics freeze

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use ubuntu-bug, it is not possible to join nvidia-bug-report because 
the application dont give me the hand to finish the report.
  When i try to execute nvidia-bug-report, i have the same thing.

  To use the PC, i have to use nouveau drivers and intel Xe GPU with
  poor performances ...

  Thanks for help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Tue Sep 28 21:13:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
  InstallationDate: Installed on 2021-09-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Intel(R) Client Systems NUC11PHi7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PHTGL579.0063.2021.0707.1057
  dmi.board.name: NUC11PHBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M26151-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 12.19
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: PH
  dmi.product.name: NUC11PHi7
  dmi.product.sku: SWNUC11PHKi7C00
  dmi.product.version: M26149-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  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:

[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

2021-11-08 Thread H

I had this issue as well, through ALL of the 5.x kernels.  Tried everything 
mentioned in the thread here, but nothing worked other than going to 4.15 
kernel.  
This gave me suspicions it was related to something with the UEFI handoff to 
OS, so I looked for BIOS updates and sure enough there was one from earlier 
this year.  Updated to the latest BIOS from Intel, and everything boots fine 
and working now.

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gmckeown   1647 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-08-15 (18 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd HP Wide Vision 
FHD Camera
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-25-generic N/A
   linux-backports-modules-5.0.0-25-generic  N/A
   linux-firmware1.181
  Tags:  eoan
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.25:bd05/17/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 2QH38EA#ABU
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed

2021-10-26 Thread A. H. Ismail

The issue still persists with kernel 5.13 and the impish driver
Why doesn't the maintainers of this driver use some of the code of tomaspinho 
driver? I read on Linux Mint forum that some people got bluetooth working with 
that driver.
Link to repo:
https://github.com/tomaspinho/rtl8821ce/

Link to LM forum thread:
https://forums.linuxmint.com/viewtopic.php?t=308215

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

Title:
  Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not
  probed

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  Confirmed

Bug description:
  The driver installed just fine and wifi is working but bluetooth does
  not.

  I will gladly provide further debugging information.

  Ubuntu 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 1931 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-17 (231 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: ashmem_linux
  Tags:  focal staging staging
  Uname: Linux 5.4.0-40-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version:

[Kernel-packages] [Bug 1945367] Re: [nvidia] Graphics freeze

2021-10-04 Thread j l h

Hello,
 
Since the last message, i have :
- Install KDE Desktop
- Modify parameters Xrender, OpenGL2.0, OpenGL3.0
- Try to install Nvidia drivers 470, NVIDIA drivers 460

Unfortunately, I encounter always the freeze of the screen in each
configuration and i have to  reboot my pc to get back the hand (or
connect with ssh from an other pc to do a reboot).

I'm joining 3 reports of breakdown, two with nvidia drivers 460 and one
with nvidia drivers version 470. (with command : journalctl -b-1 >
prevboot.txt)

Thank you for help

** Attachment added: "Report.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945367/+attachment/5530560/+files/Report.tar.gz

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

Title:
  [nvidia] Graphics freeze

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use ubuntu-bug, it is not possible to join nvidia-bug-report because 
the application dont give me the hand to finish the report.
  When i try to execute nvidia-bug-report, i have the same thing.

  To use the PC, i have to use nouveau drivers and intel Xe GPU with
  poor performances ...

  Thanks for help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Tue Sep 28 21:13:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
  InstallationDate: Installed on 2021-09-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Intel(R) Client Systems NUC11PHi7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PHTGL579.0063.2021.0707.1057
  dmi.board.name: NUC11PHBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M26151-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 12.19
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: PH
  dmi.product.name: NUC11PHi7
  dmi.product.sku: SWNUC11PHKi7C00
  dmi.product.version: M26149-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core

[Kernel-packages] [Bug 1945367] Re: [nvidia] Graphics freeze

2021-10-02 Thread j l h

Hello,
What is the next step ? 
Thanks

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

Title:
  [nvidia] Graphics freeze

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use ubuntu-bug, it is not possible to join nvidia-bug-report because 
the application dont give me the hand to finish the report.
  When i try to execute nvidia-bug-report, i have the same thing.

  To use the PC, i have to use nouveau drivers and intel Xe GPU with
  poor performances ...

  Thanks for help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.63.01  Tue Aug  3 
20:44:16 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Tue Sep 28 21:13:05 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Device [8086:2090]
  InstallationDate: Installed on 2021-09-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Intel(R) Client Systems NUC11PHi7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PHTGL579.0063.2021.0707.1057
  dmi.board.name: NUC11PHBi7
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M26151-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 12.19
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: PH
  dmi.product.name: NUC11PHi7
  dmi.product.sku: SWNUC11PHKi7C00
  dmi.product.version: M26149-403
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  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/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945367/+subscriptions


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

2021-09-27 Thread Robin H. Johnson

Will new media be available w/ this fix in place?

I ask because running "dkms status" or any dkms command presently
triggers this bug for me, and the only way forward I can see to being
able to fix that system is new media w/ a patched kernel.

-- 
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,
  >z_sa_hdl)) failed

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

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, >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 1937897] Re: GPIO error logs in start and dmesg after update of kernel

2021-08-28 Thread Bob H

These two error messages display when booting and closing live disk
media using 'safe graphics'

gpio gpiochip: (gpio_aaeon): tried to insert a GPIO chip with zero lines
gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22

they do not seem to upset the processes of the media

this occurs with Kubunt Impish daily builds and also with Kubuntu 2004.3
daily build

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25 which introduce some ODM patches from 
AAEON, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.
  Which fixes the issue introduced by
  Hirsute:
 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices
  Impish:
 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices

  
  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1881319] Re: [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized

2021-07-16 Thread Dolan H. Ali

Lenovo IdeaPad 5 15ARE05
- Processor: AMD® Ryzen 7 4700u with radeon graphics × 8 
- OS: Ubuntu 21.04
- GNOME: 3.38.5
- Kernel: 5.11.0-22-generic

Main issues:

* Touchpad is not working.

* Finger-print is not working.

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

Title:
  [Lenovo IdeaPad 5 15ARE05] Touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad isn't reacting at all

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andreas1223 F pulseaudio
   /dev/snd/controlC0:  andreas1223 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 29 18:05:01 2020
  InstallationDate: Installed on 2020-05-29 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  MachineType: LENOVO 81YQ
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1929731] [NEW] nvidia-settings --load-config-only does not load user settings upon login

2021-05-26 Thread Ma H

Public bug reported:

1. Release of Ubuntu | lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

2. Version of Package | apt-cache policy nvidia-settings
nvidia-settings:
  Installed: 460.39-0ubuntu0.20.04.1
  Candidate: 460.39-0ubuntu0.20.04.1
  Version table:
 *** 460.39-0ubuntu0.20.04.1 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 440.64-0ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages

3/4. Expected and Desired results
I expect my colour settings to be preserved and loaded between reboots/logins. 
While they are saved, they are not automatically loaded. Have to run 
nvidia-settings manually after login to load them.


My own comments:

I run Ubuntu 20.04, with the latest updates as of today. Clean install.

I have changed some settings in nvidia-settings (the gui panel - see
image) and changed the color settings, so that the brightness and
contrast is lower on all channels. These settings are saved to a nvidia-
settings-rc file in my home directory.

I noticed that there already is a startup script running this
(/etc/xdg/autostart/nvidia-settings-autostart.desktop), buut it does
NOT apply these settings upon login after gdm(3).

To fix it I changed a line from:
Exec=sh -c '/usr/bin/nvidia-settings --load-config-only'

To:
Exec=sh -c 'sleep 1 && /usr/bin/nvidia-settings --load-config-only'

Now my settings are applied upon logging in (albeit after 1 second).

I have tried other solutions suggested in forums such as running
"nvidia-settings --load-config-only" in xinitrc and Xsession, as well as
gdm3/PostLogin. They did not work, and I think that there simply needs
to be some sleep/timeout time before loading the settings. Why? I don't
know.

** Affects: nvidia-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: driver nvidia x11

** Attachment added: "Nvidia-settings colour settings"
   
https://bugs.launchpad.net/bugs/1929731/+attachment/5500535/+files/Screenshot%20from%202021-05-26%2018-29-35.png

** Description changed:

  1. Release of Ubuntu | lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  
  2. Version of Package | apt-cache policy nvidia-settings
  nvidia-settings:
-   Installed: 460.39-0ubuntu0.20.04.1
-   Candidate: 460.39-0ubuntu0.20.04.1
-   Version table:
-  *** 460.39-0ubuntu0.20.04.1 500
- 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  440.64-0ubuntu1 500
- 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 460.39-0ubuntu0.20.04.1
+   Candidate: 460.39-0ubuntu0.20.04.1
+   Version table:
+  *** 460.39-0ubuntu0.20.04.1 500
+ 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  440.64-0ubuntu1 500
+ 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  3/4. Expected and Desired results
  I expect my colour settings to be preserved and loaded between 
reboots/logins. While they are saved, they are not automatically loaded. Have 
to run nvidia-settings manually after login to load them.
  
  
  My own comments:
  
  I run Ubuntu 20.04, with the latest updates as of today. Clean install.
  
  I have changed some settings in nvidia-settings (the gui panel - see
  image) and changed the color settings, so that the brightness and
  contrast is lower on all channels. These settings are saved to a nvidia-
  settings-rc file in my home directory.
  
  I noticed that there already is a startup script running this
  (/etc/xdg/autostart/nvidia-settings-autostart.desktop), buut it does
  NOT apply these settings upon login after gdm(3).
  
  To fix it I changed a line from:
  Exec=sh -c '/usr/bin/nvidia-settings --load-config-only'
  
  To:
- Exec=sh -c 'sleep 5 && /usr/bin/nvidia-settings --load-config-only'
+ Exec=sh -c 'sleep 1 && /usr/bin/nvidia-settings --load-config-only'
  
- Now my settings are applied upon logging in (albeit after 5 seconds).
+ Now my settings are applied upon logging in (albeit after 1 second).
  
  I have tried other solutions suggested in forums such as running
  "nvidia-settings --load-config-only" in xinitrc and Xsession, as well as
  gdm3/PostLogin. They did not work, and I think that there simply needs
  to be some sleep/timeout time before loading the settings. Why? I don't
  know.

** Summary changed:

- nvidia-settings --load-config-only does not load user settings upon login

[Kernel-packages] [Bug 1903964] Re: The installer encountered an unrecoverable error

2021-03-21 Thread Bob H

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

bug #1903378 has been reported as fixed on 2021-01-14

however this bug is present at Kubuntu daily build 2021-03-21 05:49

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

Title:
  The installer encountered an unrecoverable error

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  
  Attempting to install Kubuntu Hirsute daily ISO 
http://cdimage.ubuntu.com/kubuntu/daily-live/20201112/hirsute-desktop-amd64.iso 
the installer failed with the following error message:

  The installer encountered an unrecoverable error.A desktop session
  will now be run so that you may investgate the problem or try
  installing again.

  This error occurred immediately after booting and the running of the
  file checks before entering the installer.

  The machine invlved were :

  1. Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel
  HM76 chipset 10/100 Mbps ethernet controller integrated on system
  board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd) This machine was
  in UEFI+secure boot mode.

  2. InWin BL641 i5-10400,32GB,Intel UHD Graphics 630,Ethernet,Intel
  660p 512GB M.2 NVMe hd - this install was in a VIrtualBox machine in
  BIOS mode.

  Attached is the dmesg log file from the USB media that booted the Dell
  Inspirion machine (#1 above )

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

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

[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)

** Description changed:

  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.
  
  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
+ - 5.11.6-generic from Kernel PPA (Lenovo T14s, AMD, tested quirks only)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas
  
  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.
  
  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

Title:
  can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.

  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
  - 5.11.6-generic from Kernel PPA (Lenovo T14s, AMD, tested quirks only)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

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

[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)

** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476766/+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/1919164

Title:
  can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
  New

Bug description:
  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.

  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

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

[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)

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

Title:
  can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
  New

Bug description:
  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.

  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

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

[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)

** Attachment added: "lspci-v.txt"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476768/+files/lspci-v.txt

** Description changed:

- I tried to access an mSata disk using the ASMedia AS2115 adapter.
+ I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
+ AS2115 adapter.

This did not work with
- 5.4.0-26-generic (Lenovo T14s, AMD)
- 5.8.0-44-generic (Lenovo T14s, AMD)
- 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
- using uas and using usb-quirks 174c:1153:u, ie. disabling uas
+ - 5.4.0-26-generic (Lenovo T14s, AMD)
+ - 5.8.0-44-generic (Lenovo T14s, AMD)
+ - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
+ trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

- The errors have been similiar on all configurations.
+ The errors have been similar on all configurations.
Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

I removed the modules uas and usb-storage in both cases and modprobed
them again.

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

Title:
can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
New

Bug description:
I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
AS2115 adapter.

This did not work with
- 5.4.0-26-generic (Lenovo T14s, AMD)
- 5.8.0-44-generic (Lenovo T14s, AMD)
- 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

The errors have been similar on all configurations.
Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

I removed the modules uas and usb-storage in both cases and modprobed
them again.

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

[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)

** Attachment added: "lsusb-v.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476767/+files/lsusb-v.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/1919164

Title:
  can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
  New

Bug description:
  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.

  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

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

[Kernel-packages] [Bug 1919164] [NEW] can't use mSata Adapter (with and without uas quirks)

Public bug reported:

I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
AS2115 adapter.

This did not work with
- 5.4.0-26-generic (Lenovo T14s, AMD)
- 5.8.0-44-generic (Lenovo T14s, AMD)
- 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

The errors have been similar on all configurations.
Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

I removed the modules uas and usb-storage in both cases and modprobed
them again.

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

** Attachment added: "dmesg log when using quirks aka disabling uas"
   
https://bugs.launchpad.net/bugs/1919164/+attachment/5476764/+files/dmesg-quirks.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/1919164

Title:
  can't use mSata Adapter (with and without uas quirks)

Status in linux package in Ubuntu:
  New

Bug description:
  I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia
  AS2115 adapter.

  This did not work with
  - 5.4.0-26-generic (Lenovo T14s, AMD)
  - 5.8.0-44-generic (Lenovo T14s, AMD)
  - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port)
  trying both uas and usb-quirks 174c:1153:u, ie. disabling uas

  The errors have been similar on all configurations.
  Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port.

  I removed the modules uas and usb-storage in both cases and modprobed
  them again.

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

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

[Kernel-packages] [Bug 1915688] [NEW] Please enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS

2021-02-15 Thread Rene H. Larsen

Public bug reported:

The CONFIG_FANOTIFY_ACCESS_PERMISSIONS option is required for certain
security products, like Microsoft Defender for Endpoints, to operate
correctly. As far as I can tell, it causes no overhead (when not
actively using it), in terms of code size or startup time.

It is currently disabled in the Focal Fossa -kvm kernel:

$ grep CONFIG_FANOTIFY /boot/config-5.4.0-1032-kvm 
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set

While it is enabled in the -generic kernel:

$ grep CONFIG_FANOTIFY /boot/config-5.4.0-65-generic 
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y

The same goes for Bionic Beaver.

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

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

Title:
  Please enable CONFIG_FANOTIFY_ACCESS_PERMISSIONS

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  The CONFIG_FANOTIFY_ACCESS_PERMISSIONS option is required for certain
  security products, like Microsoft Defender for Endpoints, to operate
  correctly. As far as I can tell, it causes no overhead (when not
  actively using it), in terms of code size or startup time.

  It is currently disabled in the Focal Fossa -kvm kernel:

  $ grep CONFIG_FANOTIFY /boot/config-5.4.0-1032-kvm 
  CONFIG_FANOTIFY=y
  # CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set

  While it is enabled in the -generic kernel:

  $ grep CONFIG_FANOTIFY /boot/config-5.4.0-65-generic 
  CONFIG_FANOTIFY=y
  CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y

  The same goes for Bionic Beaver.

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

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

[Kernel-packages] [Bug 1914146] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu

2021-02-01 Thread Robert H Mann

Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zfsutils-linux 0.8.3-1ubuntu12.6
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Feb  1 18:51:48 2021
ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-12-09 (54 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: zfs-linux
Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.6
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb  1 18:51:48 2021
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-12-09 (54 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.6 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port

2020-10-23 Thread Marc H.

Maybe the issue is heat, and the chip slows down of it overheats, and
some manufacturers did not include a heatsink on it, some did.

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

Title:
  0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device
  on USB3 port

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

Bug description:
  Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in
  USB3 port yields slow performance, dmesg flooded with errors. Plugging
  on USB2 port, exact same situation otherwise, works well. This is
  reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the
  left, 2 USB2 ports on the right.

  ### When working (USB2 port)
  * ethernet auto-negociation is fast
  * mii-tool is fast (typical 0.05s)
  * few lines in dmesg
  * good performance

  ### When failing :
  * ethernet auto-negociation fails, then sometimes eventually works
  * mii-tool is slow (10s of seconds instead of 0.05s)

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m40.014s
  user  0m0.013s
  sys   0m0.006s

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m50.015s
  user  0m0.011s
  sys   0m0.011s

  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m10.051s
  user  0m0.000s
  sys   0m0.012s

  But on some attempts mii-tool is fast...
  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m0.057s
  user  0m0.011s
  sys   0m0.012s

  * DHCP eventually completes (after about 30 seconds) then ethernet works.
  * whole system behaviour feels a little sluggish (not very clear, though)
  * mii-tool still slow (10s of seconds instead of 0.05s)

  ## dmesg when failing

  Full dmesg attached.

  Specific lines with occurrence count at random point (obtained with
  "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ).

   50 ei_me :00:16.0: reset: wrong host start response
   51 ei_me :00:16.0: reset: unexpected enumeration response hbm.
   60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING
  141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Another attempt

   11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
   61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
   61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1
  925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD

    5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110
    6 net_ratelimit: 31 callbacks suppressed
    9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
   10 net_ratelimit: 30 callbacks suppressed
   14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
  232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.075364] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.199491] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.199504] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:37 n55sf-l kernel: [203182.944174] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:37 n55sf-l kernel: [203182.944178] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command

[Kernel-packages] [Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port

2020-10-23 Thread Marc H.

Just found by Google search to this post. I have the same issue on
Windows 10 with a AX88179 adapter. The adapter randomly crashes / driver
crashes under heavy load or the bandwidth suddenly drops down from
500mbit/s to around 3mbit/s. You can see the issue happening here:

https://i.imgur.com/TtWRpAE.gif

So it doesnt seem to be a Linux only issue at all. I am using the latest
driver on Windows by Asix 1.20.7.0 which doesnt do anything for 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/1269883

Title:
  0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device
  on USB3 port

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

Bug description:
  Plugging USB-to-ethernet device ID 0b95:1790 ASIX Electronics Corp. in
  USB3 port yields slow performance, dmesg flooded with errors. Plugging
  on USB2 port, exact same situation otherwise, works well. This is
  reproducible 3 out of 4 attempts. Machine has 2 USB3 ports on the
  left, 2 USB2 ports on the right.

  ### When working (USB2 port)
  * ethernet auto-negociation is fast
  * mii-tool is fast (typical 0.05s)
  * few lines in dmesg
  * good performance

  ### When failing :
  * ethernet auto-negociation fails, then sometimes eventually works
  * mii-tool is slow (10s of seconds instead of 0.05s)

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m40.014s
  user  0m0.013s
  sys   0m0.006s

  time sudo mii-tool
  eth0: no link
  eth1: 10 Mbit, half duplex, no link
  real  0m50.015s
  user  0m0.011s
  sys   0m0.011s

  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m10.051s
  user  0m0.000s
  sys   0m0.012s

  But on some attempts mii-tool is fast...
  time sudo mii-tool
  eth0: no link
  eth1: negotiated 100baseTx-FD, link ok
  real  0m0.057s
  user  0m0.011s
  sys   0m0.012s

  * DHCP eventually completes (after about 30 seconds) then ethernet works.
  * whole system behaviour feels a little sluggish (not very clear, though)
  * mii-tool still slow (10s of seconds instead of 0.05s)

  ## dmesg when failing

  Full dmesg attached.

  Specific lines with occurrence count at random point (obtained with
  "dmesg | sed 's/^//' | sort | uniq -c | sort -n" ).

   50 ei_me :00:16.0: reset: wrong host start response
   51 ei_me :00:16.0: reset: unexpected enumeration response hbm.
   60 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  100 ei_me :00:16.0: unexpected reset: dev_state = RESETTING
  141 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  214 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Another attempt

   11 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
   61 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
   61 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1
  925 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD

    5 IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0001: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x0009: -110
    6 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x000a: -110
    6 net_ratelimit: 31 callbacks suppressed
    9 IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
   10 net_ratelimit: 30 callbacks suppressed
   14 ax88179_178a 4-1:1.0 eth1: Failed to read reg index 0x: -110
   14 ax88179_178a 4-1:1.0 eth1: Failed to write reg index 0x0002: -110
  209 ax88179_178a 4-1:1.0 eth1: kevent 4 may have been dropped
  232 xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending.
  232 xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr
  610 xhci_hcd :04:00.0: ERROR Transfer event TRB DMA ptr not part of 
current TD
  809 ax88179_178a 4-1:1.0 eth1: ax88179 - Link status is: 1

  Jan 16 18:39:35 n55sf-l kernel: [203181.206451] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203181.578841] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203181.578854] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.075350] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr
  Jan 16 18:39:36 n55sf-l kernel: [203182.075364] xhci_hcd :04:00.0: A 
Set TR Deq Ptr command is pending.
  Jan 16 18:39:36 n55sf-l kernel: [203182.199491] xhci_hcd :04:00.0: 
WARN Cannot submit Set TR Deq Ptr

[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices

2020-09-07 Thread Austin Abraham A H

You're a lifesaver Kai!!

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

Title:
  Lenovo ThinkBook 14-IML Touchpad not showing up in
  /proc/bus/input/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is happening on a ThinkBook 14 IML 20RV.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1848 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 20 11:10:52 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20RV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CJCN21WW
  dmi.board.name: LVA/LVAB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr:
  dmi.product.family: ThinkBook 14-IML
  dmi.product.name: 20RV
  dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML
  dmi.product.version: Lenovo ThinkBook 14-IML
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1891579] [NEW] Security enhanced Ubuntu distribution that would maintain system integrity.

2020-08-13 Thread Clinton H

Public bug reported:

A user account allows a user to do restricted tasks. An admin account
gives a user full control of the system. If the admin has full control
of the system, the admin could cause unintentional damage. The admin
should not be allowed to damage the system. A user could be tricked into
revealing their admin password. There could be a new user called System,
that would not be accessible to the Admin. The System account would have
no login. The System account would protect the system from being
damaged.

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

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

Title:
  Security enhanced Ubuntu distribution that would maintain system
  integrity.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A user account allows a user to do restricted tasks. An admin account
  gives a user full control of the system. If the admin has full control
  of the system, the admin could cause unintentional damage. The admin
  should not be allowed to damage the system. A user could be tricked
  into revealing their admin password. There could be a new user called
  System, that would not be accessible to the Admin. The System account
  would have no login. The System account would protect the system from
  being damaged.

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

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

[Kernel-packages] [Bug 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

2020-05-17 Thread Clinton H

"I'm not particularly concerned about encryption, so I'll probably leave
it off, but maybe in your case you need some additional packages on
Ubuntu to support the self-encryption."


My drive is not encrypted.

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

Title:
  blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) unknown
  3) no error
  4) error in log app.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  htpc   9157 F pulseaudio
   /dev/snd/controlC1:  htpc   9157 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-28 (48 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lxcbr0no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-23-generic N/A
   linux-backports-modules-5.3.0-23-generic  N/A
   linux-firmware1.183.2
  RfKill:
   
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6b
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1804591] Re: tsc: Fast TSC calibration failed

2020-04-11 Thread H I Murphy

It happened to one of mys systems this morning. The system never got past the 
logo for the motherboard manufacturer (AsRock). Here is the top part of dmesg 
down to where the failure message occurred, [code]
0.00] kernel: Linux version 5.4.0-21-generic (buildd@lcy01-amd64-006) (gcc 
version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)) #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 
2020 (Ubuntu 5.4.0-21.25-generic 5.4.27)
[0.00] kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/vgxubuntu-root ro text
[0.00] kernel: KERNEL supported cpus:
[0.00] kernel:   Intel GenuineIntel
[0.00] kernel:   AMD AuthenticAMD
[0.00] kernel:   Hygon HygonGenuine
[0.00] kernel:   Centaur CentaurHauls
[0.00] kernel:   zhaoxin   Shanghai  
[0.00] kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating 
point registers'
[0.00] kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] kernel: x86/fpu: Enabled xstate features 0x7, context size is 
832 bytes, using 'compacted' format.
[0.00] kernel: BIOS-provided physical RAM map:
[0.00] kernel: BIOS-e820: [mem 0x-0x0009d3ff] 
usable
[0.00] kernel: BIOS-e820: [mem 0x0009d400-0x0009] 
reserved
[0.00] kernel: BIOS-e820: [mem 0x000e-0x000f] 
reserved
[0.00] kernel: BIOS-e820: [mem 0x0010-0x09d01fff] 
usable
[0.00] kernel: BIOS-e820: [mem 0x09d02000-0x09ff] 
reserved
[0.00] kernel: BIOS-e820: [mem 0x0a00-0x0a1f] 
usable
[0.00] kernel: BIOS-e820: [mem 0x0a20-0x0a20afff] 
ACPI NVS
[0.00] kernel: BIOS-e820: [mem 0x0a20b000-0x0aff] 
usable
[0.00] kernel: BIOS-e820: [mem 0x0b00-0x0b01] 
reserved
[0.00] kernel: BIOS-e820: [mem 0x0b02-0xdaaf5fff] 
usable
[0.00] kernel: BIOS-e820: [mem 0xdaaf6000-0xdbfe7fff] 
reserved
[0.00] kernel: BIOS-e820: [mem 0xdbfe8000-0xdc169fff] 
usable
[0.00] kernel: BIOS-e820: [mem 0xdc16a000-0xdc57dfff] 
ACPI NVS
[0.00] kernel: BIOS-e820: [mem 0xdc57e000-0xdd0c5fff] 
reserved
[0.00] kernel: BIOS-e820: [mem 0xdd0c6000-0xdeff] 
usable
[0.00] kernel: BIOS-e820: [mem 0xdf00-0xdfff] 
reserved
[0.00] kernel: BIOS-e820: [mem 0xf800-0xfbff] 
reserved
[0.00] kernel: BIOS-e820: [mem 0xfd00-0x] 
reserved
[0.00] kernel: BIOS-e820: [mem 0x0001-0x00041f37] 
usable
[0.00] kernel: NX (Execute Disable) protection: active
[0.00] kernel: SMBIOS 3.2.1 present.
[0.00] kernel: DMI: To Be Filled By O.E.M. To Be Filled By 
O.E.M./B450M/ac, BIOS P1.50 10/14/2019
[0.00] kernel: tsc: Fast TSC calibration failed
[/code]

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

Title:
  tsc: Fast TSC calibration failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.00] APIC: Switch to symmetric I/O mode setup
  [0.004000] Switched APIC routing to physical flat.
  [0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
  [0.024000] tsc: Fast TSC calibration failed
  [0.032000] tsc: PIT calibration matches HPET. 1 loops
  [0.032000] tsc: Detected 3600.039 MHz processor
  [0.032000] clocksource: tsc-early: mask: 0x max_cycles: 
0x33e47874cac, max_idle_ns: 440795311274 ns
  [0.032000] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 7200.07 BogoMIPS (lpj=14400156)
  [0.032000] pid_max: default: 32768 minimum: 301
  [0.032000] Security Framework initialized
  [0.032000] Yama: becoming mindful.
  [0.032000] AppArmor: AppArmor initialized
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1: 1438 F pulseaudio
   /dev/snd/controlC0: 1438 F pulseaudio
  CurrentDesktop: LXQt
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-11-22 (2 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Micro-Star International Co., Ltd. MS-7A39
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=x ro 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1865962] Re: Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware

2020-03-30 Thread Kevin H. Smith

Not sure if this is the right place, but I've had the no wifi problem on
my Asus Eee PC (Intel Atom) for both revisions since 5.3.0-28 generic
(IOW, that's the last one that works properly, but there have been 2 new
revisions installed since in my Peppermint 10 distro). I'm getting
worried that the last working version will rotate out of use in this
problem is not fixed soon.

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

Title:
  Dell XPS 13 9300 Intel 1650S wifi [34f0:1651] fails to load firmware

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  It dumps some debug messages while loading iwlwifi firmware every time after 
booted up and finally got below errors
     [5.632845] iwlwifi :00:14.3: Failed to start RT ucode: -110
     [5.632849] iwlwifi :00:14.3: Firmware not running - cannot dump 
error
     [5.645491] iwlwifi :00:14.3: Failed to run INIT ucode: -110

  [Fix]
  It looks like it fails to load the firmware since mainline v5.4 kernel, and 
got fixed at v5.6-rc1. After bisect the kernel, the first bad commit is
     b3bd6416fc77 iwlwifi: assume the driver_data is a trans_cfg, but allow 
full cfg

  To avoid conflicts, we have to backport the following commits from mainline 
kernel
     b81b7bd02eda iwlwifi: remove some outdated iwl22000 configurations
     c042f0c77f3d iwlwifi: allocate more receive buffers for HE devices
     5661925a9b38 iwlwifi: pcie: rx: use rxq queue_size instead of constant
     bfc3e9fdbfb8 iwlwifi: 22000: fix some indentation
     3681021fc6af iwlwifi: remove IWL_DEVICE_22560/IWL_DEVICE_FAMILY_22560

  [Test]
  Verified on Dell XPS 9300 with Killer AX1650i wifi card and XPS 13 2-1 
platform, wifi keeps working after reboot 10 times.

  [Regression Potential]
  Medium, the code changes a lot, although the test results are all positive, 
it's still hard to evaluate the regression potential.

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

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

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

2020-03-28 Thread Clinton H

https://gitlab.freedesktop.org/drm/amd/issues/968

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #968
   https://gitlab.freedesktop.org/drm/amd/issues/968

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

2020-03-28 Thread Clinton H

In the post above I am using 5.6.0-994-generic.

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized successfully.
   7:53:47 AM kernel: [drm] ring test on 5 succeeded in 1 usecs

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

2020-03-17 Thread Clinton H

I have not received the *ERROR* radeon: failed testing IB on ring 5
(-110) message recently. Instead, sometimes when my computer wakes from
sleep there is a blank screen. If I press the sleep button on my
keyboard or the power button on my computer, nothing happens. I have to
press the restart button.

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

2020-01-07 Thread Clinton H

I assume I need to install the following:

linux-headers-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb
linux-image-unsigned-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb
linux-modules-5.5.0-994-generic_5.5.0-994.202001070537_amd64.deb


Do I need to install the following:

0001-base-packaging.patch
0002-UBUNTU-SAUCE-add-vmlinux.strip-to-BOOT_TARGETS1-on-p.patch
0003-UBUNTU-SAUCE-tools-hv-lsvmbus-add-manual-page.patch
0004-debian-changelog.patch
0005-configs-based-on-Ubuntu-5.5.0-3.4.patch

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of

[Kernel-packages] [Bug 1858254] Re: thermald: [ERR]THD engine start failed

2020-01-03 Thread Clinton H

** Description changed:

  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.
  
+ Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
+ Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
- Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
- Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
- 
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

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

Title:
  thermald: [ERR]THD engine start failed

Status in thermald package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.

  Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...
  Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

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

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

[Kernel-packages] [Bug 1858254] [NEW] thermald: [ERR]THD engine start failed

2020-01-03 Thread Clinton H

Public bug reported:

1) Ubuntu 19.10
2) 1.9
3) No error in log app.
4) See error below.

Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: signature 
and/or required key missing - tainting kernel
Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...

Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external entity 
"/etc/thermald/thermal-conf.xml"

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

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

Title:
  thermald: [ERR]THD engine start failed

Status in thermald package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1.9
  3) No error in log app.
  4) See error below.

  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM systemd: Started GRUB failed boot detection.
  Dec 29 2019  9:28:21 PM kernel: vboxdrv: module verification failed: 
signature and/or required key missing - tainting kernel
  Dec 29 2019  9:28:18 PM systemd: Starting GRUB failed boot detection...

  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: [ERR]THD engine start failed
  Dec 29 2019  9:28:26 PM thermald: I/O warning : failed to load external 
entity "/etc/thermald/thermal-conf.xml"

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

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

[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected

2020-01-03 Thread Magne H

The following did the job for me. Remember to change the headset to AD2P
under SOUNDS in Ubuntu on your headset.

---

Ref. from source:

https://askubuntu.com/questions/1139404/sony-noise-cancelling-
headphones-wh-1000xm2-3-and-bluetooth-initial-autoconnec

---

The "ambient noise" you're hearing is a loopback from your computer's
mic coming out through your headphones.

This is apparently due to a bug with A2DP's implementation.

I fixed this in Ubuntu 19.04 by installing Blueman and pairing my
headphones as an Audio Sink rather than a headset:

Unpair your headphones, if they're currently paired.
sudo apt install blueman
Open Blueman, click on "search".
Select your headphones, right click, select "Setup"
Make sure they're paired as an Audio Sink rather than a Headset
Select your headphones as an audio output in your sound settings

If you have Spotify open throughout the process you have to restart it.

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

Title:
  Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low
  quality headset mode and fails to switch to A2DP when selected

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1857394] Re: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg

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

apport information

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

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1:

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1857394/+attachment/5316384/+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/1857394

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14:

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14:

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1857394/+attachment/5316386/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1:

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1:

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

apport information

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

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14:

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1857394/+attachment/5316376/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14:

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1857394/+attachment/5316374/+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/1857394

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14:

[Kernel-packages] [Bug 1857394] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1857394/+attachment/5316380/+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/1857394

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1:

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

apport information

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

** Description changed:

  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.
  
  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x10: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: [1002:439c] type 00 class 0x01018a
   4:47:59 PM kernel: pci :00:14.0: [1002:4385] type 00 class 0x0c0500
   4:47:59 PM

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

apport information

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

Title:
  [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.

  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci

[Kernel-packages] [Bug 1857394] Re: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)

apport information

** Description changed:

  1) Ubuntu 19.10
  2) kernel 5.3.0-23-generic
  3) No error.
  4) Error in Ubuntu Logs App.
  
  Message:
  4:47:59 PM kernel: pci :00:14.4:   bridge window [mem 
0xd000-0xfebf window] (subtractive decode)
   4:47:59 PM kernel: pci_bus :04: extended config space not accessible
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfdd0-0xfddf 64bit pref]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [mem 
0xfde0-0xfdef]
   4:47:59 PM kernel: pci :00:0a.0:   bridge window [io  0xc000-0xcfff]
   4:47:59 PM kernel: pci :00:0a.0: PCI bridge to [bus 03]
   4:47:59 PM kernel: pci :03:00.0: PME# supported from D0 D1 D2 D3hot 
D3cold
   4:47:59 PM kernel: pci :03:00.0: supports D1 D2
   4:47:59 PM kernel: pci :03:00.0: reg 0x30: [mem 0x-0x 
pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x20: [mem 0xfdde-0xfdde 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x18: [mem 0xfddff000-0xfddf 
64bit pref]
   4:47:59 PM kernel: pci :03:00.0: reg 0x10: [io  0xce00-0xceff]
   4:47:59 PM kernel: pci :03:00.0: [10ec:8168] type 00 class 0x02
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfa00-0xfbff 64bit pref]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [mem 
0xfdf0-0xfdff]
   4:47:59 PM kernel: pci :00:06.0:   bridge window [io  0xd000-0xdfff]
   4:47:59 PM kernel: pci :00:06.0: PCI bridge to [bus 02]
   4:47:59 PM kernel: pci :02:00.0: disabling ASPM on pre-1.1 PCIe device.  
You can enable it with 'pcie_aspm=force'
   4:47:59 PM kernel: pci :02:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :02:00.0: reg 0x18: [mem 0xfa00-0xfbff 
64bit pref]
   4:47:59 PM kernel: pci :02:00.0: reg 0x10: [mem 0xfdf0-0xfdff 
64bit]
   4:47:59 PM kernel: pci :02:00.0: [1002:4d51] type 00 class 0x048000
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xd000-0xdfff 64bit pref]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [mem 
0xfda0-0xfdaf]
   4:47:59 PM kernel: pci :00:02.0:   bridge window [io  0xe000-0xefff]
   4:47:59 PM kernel: pci :00:02.0: PCI bridge to [bus 01]
   4:47:59 PM kernel: pci :01:00.1: supports D1 D2
   4:47:59 PM kernel: pci :01:00.1: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.1: reg 0x10: [mem 0xfdafc000-0xfdaf 
64bit]
   4:47:59 PM kernel: pci :01:00.1: [1002:aa38] type 00 class 0x040300
   4:47:59 PM kernel: pci :01:00.0: supports D1 D2
   4:47:59 PM kernel: pci :01:00.0: enabling Extended Tags
   4:47:59 PM kernel: pci :01:00.0: reg 0x30: [mem 0x-0x0001 
pref]
   4:47:59 PM kernel: pci :01:00.0: reg 0x20: [io  0xee00-0xeeff]
   4:47:59 PM kernel: pci :01:00.0: reg 0x18: [mem 0xfdae-0xfdae 
64bit]
   4:47:59 PM kernel: pci :01:00.0: reg 0x10: [mem 0xd000-0xdfff 
64bit pref]
   4:47:59 PM kernel: pci :01:00.0: [1002:9540] type 00 class 0x03
   4:47:59 PM kernel: pci :00:18.3: [1022:1103] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.2: [1022:1102] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.1: [1022:1101] type 00 class 0x06
   4:47:59 PM kernel: pci :00:18.0: [1022:1100] type 00 class 0x06
   4:47:59 PM kernel: pci :00:14.5: reg 0x10: [mem 0xfe028000-0xfe028fff]
   4:47:59 PM kernel: pci :00:14.5: [1002:4399] type 00 class 0x0c0310
   4:47:59 PM kernel: pci :00:14.4: [1002:4384] type 01 class 0x060401
   4:47:59 PM kernel: pci :00:14.3: [1002:439d] type 00 class 0x060100
   4:47:59 PM kernel: pci :00:14.2: PME# supported from D0 D3hot D3cold
   4:47:59 PM kernel: pci :00:14.2: reg 0x10: [mem 0xfe024000-0xfe027fff 
64bit]
   4:47:59 PM kernel: pci :00:14.2: [1002:4383] type 00 class 0x040300
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x1c: [io  0x0376]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x18: [io  
0x0170-0x0177]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x14: [io  0x03f6]
   4:47:59 PM kernel: pci :00:14.1: legacy IDE quirk: reg 0x10: [io  
0x01f0-0x01f7]
   4:47:59 PM kernel: pci :00:14.1: reg 0x20: [io  0xfa00-0xfa0f]
   4:47:59 PM kernel: pci :00:14.1: reg 0x1c: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x18: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: reg 0x14: [io  0x-0x0003]
   4:47:59 PM kernel: pci :00:14.1: reg 0x10: [io  0x-0x0007]
   4:47:59 PM kernel: pci :00:14.1: [1002:439c] type 00 class 0x01018a
   4:47:59 PM kernel: pci :00:14.0: [1002:4385] type 00 class 0x0c0500
   4:47:59 PM kernel: pci :00:13.2: PME# supported from D0 D1 D2 D3hot
   4:47:59 PM kernel: pci :00:13.2: supports D1 D2
   4:47:59

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized successfully.
   7:53:47 AM kernel: [drm] ring test on 5

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1857730/+attachment/5316361/+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/1857730

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized

[Kernel-packages] [Bug 1857730] Re: [drm:radeon_ib_ring_tests [radeon]] ERROR radeon: failed testing IB on ring 5 (-110).

apport information

** Tags added: apport-collected wayland-session

** Description changed:

  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.
  
  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized successfully.
   7:53:47 AM kernel: [drm] ring test on 5 succeeded in 1 usecs
   7:53:47 AM kernel: [drm] ring test on 3 succeeded in 2 usecs
   7:53:47 AM kernel: [drm] ring test on 0 succeeded in 1 usecs
   7:53:47 AM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   7:53:47 AM kernel: [drm] enabling PCIE gen 2 link speeds, disable with

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD initialized

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm]

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm]

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel:

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm]

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

apport information

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

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD

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

apport information

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

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD

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

apport information

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

Title:
  [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB
  on ring 5 (-110).

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) GDM 3.34.1
  3) Resume from standby without error and corrupt screen graphics.
  4) Randomly there is an error after resuming from standby and corrupt screen 
graphics.

  4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:38:15 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 5 succeeded
   4:37:02 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:37:02 PM kernel: [drm] UVD initialized successfully.
   4:37:02 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:37:02 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:37:02 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:37:02 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:12 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:36:11 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:36:01 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:36:01 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:36:01 PM kernel: [drm] UVD initialized successfully.
   4:36:01 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:36:01 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:36:01 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:36:01 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:55 PM gdm-x-session: (II) RADEON(0): glamor X acceleration enabled on 
AMD RV710 (DRM 2.50.0 / 5.3.0-24-generic, LLVM 9.0.0)
   4:34:54 PM gdm-x-session: (II) xfree86: Adding drm device (/dev/dri/card0)
   4:34:46 PM gnome-shell: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 42 
failed: Permission denied
   4:34:45 PM kernel: [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: 
failed testing IB on ring 5 (-110).
   4:34:45 PM kernel: [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence 
wait timed out.
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   4:34:45 PM kernel: [drm] UVD initialized successfully.
   4:34:45 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   4:34:45 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   4:34:45 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   4:34:45 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   2:15:55 PM kernel: [drm] ib test on ring 5 succeeded
   2:15:55 PM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   2:15:55 PM kernel: [drm] UVD initialized successfully.
   2:15:55 PM kernel: [drm] ring test on 5 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] ring test on 3 succeeded in 2 usecs
   2:15:55 PM kernel: [drm] ring test on 0 succeeded in 1 usecs
   2:15:55 PM kernel: [drm] PCIE GART of 1024M enabled (table at 
0x0014C000).
   2:15:55 PM kernel: [drm] enabling PCIE gen 2 link speeds, disable with 
radeon.pcie_gen2=0
   7:53:47 AM kernel: [drm] ib test on ring 5 succeeded
   7:53:47 AM kernel: [drm] ib test on ring 3 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] ib test on ring 0 succeeded in 0 usecs
   7:53:47 AM kernel: [drm] UVD

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