[Kernel-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Please try this: sudo apt update sudo apt install linux-generic-hwe-20.04 and then reboot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Good news: This is only happening in kernel 5.4-5.6. No reports from kernel 5.8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
I've logged it for you: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914573] Re: kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug is no longer a duplicate of bug 1907142 [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914573 Title: kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 ... and then the display server crashes Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915322] Re: System freezes on resume from sleep
Next please try an older kernel series like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.97/ ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Incomplete ** Summary changed: - System freezes on resume from sleep + [nvidia] System freezes on resume from sleep -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: [nvidia] System freezes on resume from sleep Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Kernel-packages] [Bug 1915322] Re: System freezes on resume from sleep
Thanks. It appears there's a hardware or kernel problem when resuming from sleep: Feb 10 23:13:49 Garitchnekig systemd-journald[265]: Missed 850 kernel messages Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 Feb 10 23:13:49 Garitchnekig kernel: pcieport :00:1c.0: AER: Multiple Uncorrected (Fatal) error received: :01:00.1 So it's not a Xorg or Gnome Shell bug. I will assign it to the kernel and also to the Nvidia driver, which runs in the kernel. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Incomplete => New ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.8-gfx -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: [nvidia] System freezes on resume from sleep Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1907808] Re: my mouse isnt alway working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907808 Title: my mouse isnt alway working Status in linux package in Ubuntu: Expired Bug description: I am using a macbook pro for this ubuntu distro on a 61 gb partition. I realize macbooks are terrible for linux however I felt like giving it a try, the trackpad was working on some start ups but seems not to be anymore at all. I saw online that reporting this issue is possible from terminal, so i figured it would be the correct thing to do. Anyway I shall try to find a solution now ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: felix 1036 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 12:30:12 2020 InstallationDate: Installed on 2020-12-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M MachineType: Apple Inc. MacBookPro14,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=18a8c951-82bf-4733-8f17-b447f26b0e8e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 429.50.1.0.0 dmi.board.name: Mac-B4831CEBD52A0C4C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B4831CEBD52A0C4C dmi.modalias: dmi:bvnAppleInc.:bvr429.50.1.0.0:bd10/19/2020:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915322] Re: System freezes on resume from sleep
Alright, Done! I did notice that the - dissapears from the top left of the screen after pressing ctl/alt/f2 , in case that helps at all. I've attatched the new prevboot.txt: ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915322/+attachment/5462537/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: System freezes on resume from sleep Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Kernel-packages] [Bug 1915322] Re: Xorg freeze
Thanks. The log in comment #3 shows the system did not return from sleep. Please try again, resuming from sleep (even if it doesn't respond), wait about 30 seconds, reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Summary changed: - Xorg freeze + System freezes on resume from sleep -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: System freezes on resume from sleep Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers:
[Kernel-packages] [Bug 1915322] Re: Xorg freeze
I also followed the instructions on the link you sent me, i took a screenshot of the crashes it had: ** Attachment added: "Screenshot from 2021-02-10 22-26-09.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915322/+attachment/5462531/+files/Screenshot%20from%202021-02-10%2022-26-09.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: Xorg freeze Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Kernel-packages] [Bug 1915322] Re: Xorg freeze
Hey, Unfortunately ctl+alt+f1 or f2 did not fix the bug. I've included the .txt file that resulted from the command you gave me. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915322/+attachment/5462530/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: Xorg freeze Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.10-rc1. commit 2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 Author: Xiao Ni Date: Tue Aug 25 13:42:59 2020 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/2628089b74d5a64bd0bcb5d247a18f78d7b6f4d0 commit 8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 Author: Xiao Ni Date: Tue Aug 25 13:43:00 2020 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/8650a889017cb1f6ea6813ccf83a2e9f6fa49dd3 commit f046f5d0d79cdb968f219ce249e497fd1accf484 Author: Xiao Ni Date: Tue Aug 25 13:43:01 2020 +0800 Subject: md/raid10: pull codes that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f046f5d0d79cdb968f219ce249e497fd1accf484 commit bcc90d280465ebd51ab8688be86e1f00c62dccf9 Author: Xiao Ni Date: Wed Sep 2 20:00:22 2020 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/bcc90d280465ebd51ab8688be86e1f00c62dccf9 commit d3ee2d8415a6256c1c41e1be36e80e640c3e6359 Author: Xiao Ni Date: Wed Sep 2 20:00:23 2020 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/d3ee2d8415a6256c1c41e1be36e80e640c3e6359 There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commits enable Radid10 to use large discards, instead of splitting into many bios, since the technical hurdles have now been removed. commit e0910c8e4f87bb9f767e61a778b0d9271c4dc512 Author: Mike Snitzer Date: Thu Sep 24 13:14:52 2020 -0400 Subject: dm raid: fix discard limits for raid1 and raid10 Link: https://github.com/torvalds/linux/commit/e0910c8e4f87bb9f767e61a778b0d9271c4dc512 commit f0e90b6c663a7e3b4736cb318c6c7c589f152c28 Author: Mike Snitzer Date: Thu Sep 24 16:40:12 2020 -0400 Subject: dm raid: remove unnecessary discard limits for raid10 Link: https://github.com/torvalds/linux/commit/f0e90b6c663a7e3b4736cb318c6c7c589f152c28 All the commits mentioned follow a similar strategy which was implemented in Raid0 in the below commit, which was merged in 4.12-rc2, which fixed block discard performance issues in Raid0: commit 29efc390b9462582ae95eb9a0b8cd17ab956afc0 Author: Shaohua Li Date: Sun May 7 17:36:24 2017 -0700 Subject: md/md0: optimize raid0 discard handling Link: https://github.com/torvalds/linux/commit/29efc390b9462582ae95eb9a0b8cd17ab956afc0 The commits more or less cherry pick to the 5.8, 5.4 and 4.15 kernels, with the following minor fixups: 1)
[Kernel-packages] [Bug 1915322] Re: Xorg freeze
Thanks for the bug report. Next time the freeze happens, please try Ctrl+Alt+F1 or F2 to find the login screen. If that doesn't work then please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also try these instructions in case the freeze is due to something crashing: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: nvidia ** Tags added: hybrid ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => nvidia-graphics-drivers-460 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915322 Title: Xorg freeze Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47
[Kernel-packages] [Bug 1915322] [NEW] Xorg freeze
You have been subscribed to a public bug: Hey guys! First up, I've been using ubuntu on and off since I was about twelve, and I love this os.Thank you guys for the hard work! Second, I've been having an unfortunate bug on my laptop for quite some time now. I'm using an acer aspire e5-575g-55nw and every time my laptop goes into suspend, I can't get back to any kind of GUI after waking it up, instead going to a black screen with a single blinking white - symbol in the top left corner. i've tried just about every fix I could find on the internet, without being able to find any way back to my login screen or desktop. Note that this does not happen when my laptop goes to sleep on it's own after a set ammount of time, only when i put it into suspend or close the lid. I hope I included enough information, please let me know if you need any other information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 15:15:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] Acer Aspire E5-575G [1025:1094] InstallationDate: Installed on 2021-02-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57f2 Realtek Semiconductor Corp. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f1010786-e2a1-44b4-a3b8-6a48523960df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.release: 1.47 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:br1.47:efr2.50:svnAcer:pnAspireE5-575G:pvrV1.47:rvnAcer:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.47 dmi.product.version: V1.47 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-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 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal freeze hybrid nvidia ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1915322 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. -- Mailing list:
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
@vicamo At this time the kernel is available in proposed.
I can confirm that the kernel 5.8.0-44, in proposed, solves the problem
in Groovy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload
Performing verification for Focal. The affected user enabled -proposed and installed 5.4.0-66-generic to the system with a QLogic FastLinQ QL41000 Series 10/25/40/50GbE Controller. They then set all interfaces down, and brought up the QLogic NIC only. # uname -rv 5.4.0-66-generic #74~18.04.2-Ubuntu SMP Fri Feb 5 11:17:31 UTC 2021 # nslookup internal.kubernetes.domain.example 10.1.0.10 Server: 10.1.0.10 Address: 10.1.0.10#53 Name: internal.kubernetes.domain.example Address: 10.48.24.11 # ethtool -k eno1 | grep tx-checksumming tx-checksumming: on # ethtool -k enp94s0f0 | grep tx-checksumming tx-checksumming: on DNS lookup to an internal kubernetes domain with IPIP type DNS lookups work as intended, with tx checksumming enabled. The kernel in -proposed fixes the issue, marking as verified. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909062 Title: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1909062 [Impact] For users with QLogic QL41xxx series NICs, such as the FastLinQ QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the 4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will fail, due to these packets getting corrupted. Kubernetes uses IPIP tunnelled packets for internal DNS resolution, and this particular packet type is not supported for hardware tx checksum offload, and the packets end up corrupted when the qede driver attempts to checksum them. This only affects internal Kubernetes DNS, as regular DNS lookups to regular external domains will succeed, due to them not using IPIP packet types. [Fix] Marvell has developed a fix for the qede driver, which checks the packet type, and if it is IPPROTO_IPIP, then csum offloads are disabled for socket buffers of type IPIP. commit 5d5647dad259bb416fd5d3d87012760386d97530 Author: Manish Chopra Date: Mon Dec 21 06:55:30 2020 -0800 Subject: qede: fix offload for IPIP tunnel packets Link: https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530 This commit landed in mainline in 5.11-rc3. The commit was accepted into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7. Note, this SRU isn't targeted for Bionic due to tx csum offload support only landing in 5.0 and onward, meaning the 4.15 kernel still works even without this patch. Because of this, Bionic can pick the patch up naturally from upstream stable. [Testcase] The system must have a QLogic QL41xxx series NIC fitted, and needs to be a part of a Kubernetes cluster. Firstly, get a list of all devices in the system: $ sudo ifconfig Next, set all devices down with: $ sudo ifconfig down Next, bring up the QLogic QL41xxx device: $ sudo ifconfig up Then, attempt to lookup an internal Kubernetes domain: $ nslookup Without the patch, the connection will time out: ;; connection timed out; no servers could be reached If we look at packet traces with tcpdump, we see it leaves the source, but never arrives at the destination. There is a test kernel available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test If you install it, then Kubernetes internal DNS lookups will succeed. [Where problems could occur] If a regression were to occur, then users of the qede driver would be affected. This is limited to those with QLogic QL41xxx series NICs. The patch explicitly checks for IPIP type packets, so only those particular packets would be affected. Since IPIP type packets are uncommon, it would not cause a total outage on regression, since most packets are not IPIP tunnelled. It could potentially cause problems for users who frequently handle VPN or Kubernetes internal DNS traffic. A workaround would be to use ethtool to disable tx csum offload for all packet types, or to revert to an older kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915340] [NEW] package zfs-dkms 0.8.4-1ubuntu11.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: install zfs-dkms on ubuntu with kernel 5.11.0-rc7 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms 0.8.4-1ubuntu11.1 Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: zfs-dkms:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 10 23:23:26 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.4-1ubuntu11.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- 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/1915340 Title: package zfs-dkms 0.8.4-1ubuntu11.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: New Bug description: install zfs-dkms on ubuntu with kernel 5.11.0-rc7 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms 0.8.4-1ubuntu11.1 Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: zfs-dkms:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 10 23:23:26 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.4-1ubuntu11.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 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/1915340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903848] Re: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1903848 Title: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working Status in linux-signed package in Ubuntu: Confirmed Bug description: This seems to be a persistent problem that has been around a few kernel versions earlier (see i.e.: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757 ). After yesterday's apt update to 5.4.0-53-generic (amd64), my USB webcam (Logitech c930) as well as my internal audio (Intel HDA) stopped working altogether. All I get is a dummy audio output from the list of devices, and the webcam is not working either. I can still see my pre-existing audio devices with 'lspci | grep Audio': 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) 'inxi -SA' reports this: Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio driver: N/A Device-2: NVIDIA GP104 High Definition Audio driver: N/A (The #2 NVIDIA one being the video card's audio option, which I don't use, but it's not listed as being available either.) However, i.e. 'pacmd -list-cards' says: 0 card(s) available. There's been plenty of similar instances of this error in 20.04.x and it has been tried to have been solved in threads such as: #1 https://askubuntu.com/questions/1258510/only-dummy-output-sound-in- ubuntu-20-04-after-reboot-broken-driver-modul #2 https://www.linuxuprising.com/2018/06/fix-no-sound-dummy-output- issue-in.html From #2, if I try: 'lsmod | grep snd_hda_intel' (That displays no results at all.) However, this one does bring results: 'lspci -nnk | grep -A2 Audio' 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) DeviceName: Intel(R) High Definition Audio Device Subsystem: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:0034] Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) -- 01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) Subsystem: NVIDIA Corporation GP104 High Definition Audio Controller [10de:11a3] Kernel modules: snd_hda_intel I've been trying all the available fixes at the forementioned url #2 to no avail, and also been trying to revert them, to no avail. I've been trying to run ALSA's configuration and it seems that the ALSA modules are not loading. Also been trying out various fix proposals from people who've had the same issue, but no luck on that frontier. Anyway, now I'm stuck with no webcam, no audio. Any suggestions? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1903848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881757] Re: webcam is detected but not working with kernel 5.4.0.33
Camera still not working for me: $ uname -a Linux xps13-michid 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1881757 Title: webcam is detected but not working with kernel 5.4.0.33 Status in linux-signed package in Ubuntu: Fix Released Bug description: webcam is detected not working under kernel 5.4.0.33 and 5.4.0.31 . The webcam is functional with kernels 5.0 and 5.6.15 . -usb:1 description: Video product: USB 2.0 Web Camera vendor: Alcor Micro, Corp. physical id: 2 bus info: usb@1:1.2 version: 0.08 capabilities: usb-2.00 configuration: driver=uvcvideo maxpower=200mA speed=480Mbit/s susb; lsb_release -a; uname -a Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1d0b:0021 HAN HUA CABLE & WIRE TECHNOLOGY (J.X.) CO., LTD. Bus 001 Device 003: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux afsal-Excelance 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux more info : https://answers.launchpad.net/ubuntu/+question/691070 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1881757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915332] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1915332/+attachment/5462438/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1915332
Title:
Vulkaninfo crashes on dual gpu setup
Status in nvidia-graphics-drivers-460 package in Ubuntu:
New
Bug description:
Hi!
First, I should mention that the driver in general works very well and
I have not encountered other problems with it.
I noticed however that vulkaninfo (from vulkan-tools) is not able to
run. I think it is either related to Wayland or my prime
configuration. I tried with both XWayland and Wayland.
```
~/dev/Vulkan-Tools/build master ❯ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
ERROR at
/build/vulkan-tools-A4vpMj/vulkan-tools-1.2.162.0+dfsg1/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfaceFormats2KHR
failed with ERROR_INITIALIZATION_FAILED
~/dev/Vulkan-Tools/build master ❯ env DISPLAY= vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
'DISPLAY' environment variable not set... skipping surface info
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
fish: “env DISPLAY= vulkaninfo” terminated by signal SIGSEGV (Address
boundary error)
```
I then built vulkaninfo from source. The backtrace is not very helpful
though, it crashes somewhere inside the NVIDIA egl libraries.
```
Thread 1 "vulkaninfo" received signal SIGSEGV, Segmentation fault.
0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
(gdb) bt
#0 0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#1 0x7fffed8041f0 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#2 0x555cd723 in GetVectorInit (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 ,
init=VK_PRESENT_MODE_IMMEDIATE_KHR) at vulkaninfo/vulkaninfo.h:247
#3 0x555bcc37 in GetVector (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 )
at vulkaninfo/vulkaninfo.h:259
#4 0x555b42d5 in AppSurface::AppSurface (this=0x55ecc090,
inst=..., phys_device=0x55eca990, surface_extension=...,
sur_extension_pNextChain=std::vector of length 2, capacity 2 = {...})
at vulkaninfo/vulkaninfo.h:1217
#5 0x555abeb5 in main (argc=1, argv=0x7fffde98) at
vulkaninfo/vulkaninfo.cpp:948
```
Any idea what this could be caused by? I provide core dumps if that is
helpful.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2020-09-22 (141 days ago)
InstallationMedia:
NonfreeKernelModules: nvidia_modeset nvidia
Package: nvidia-driver-460 460.39-0ubuntu1 [origin: unknown]
PackageArchitecture: amd64
ProcEnviron:
TERM=tmux-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Tags: third-party-packages hirsute wayland-session
Uname: Linux 5.10.0-14-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bumblebee sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915332/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915332] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1915332/+attachment/5462437/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1915332
Title:
Vulkaninfo crashes on dual gpu setup
Status in nvidia-graphics-drivers-460 package in Ubuntu:
New
Bug description:
Hi!
First, I should mention that the driver in general works very well and
I have not encountered other problems with it.
I noticed however that vulkaninfo (from vulkan-tools) is not able to
run. I think it is either related to Wayland or my prime
configuration. I tried with both XWayland and Wayland.
```
~/dev/Vulkan-Tools/build master ❯ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
ERROR at
/build/vulkan-tools-A4vpMj/vulkan-tools-1.2.162.0+dfsg1/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfaceFormats2KHR
failed with ERROR_INITIALIZATION_FAILED
~/dev/Vulkan-Tools/build master ❯ env DISPLAY= vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
'DISPLAY' environment variable not set... skipping surface info
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
fish: “env DISPLAY= vulkaninfo” terminated by signal SIGSEGV (Address
boundary error)
```
I then built vulkaninfo from source. The backtrace is not very helpful
though, it crashes somewhere inside the NVIDIA egl libraries.
```
Thread 1 "vulkaninfo" received signal SIGSEGV, Segmentation fault.
0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
(gdb) bt
#0 0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#1 0x7fffed8041f0 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#2 0x555cd723 in GetVectorInit (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 ,
init=VK_PRESENT_MODE_IMMEDIATE_KHR) at vulkaninfo/vulkaninfo.h:247
#3 0x555bcc37 in GetVector (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 )
at vulkaninfo/vulkaninfo.h:259
#4 0x555b42d5 in AppSurface::AppSurface (this=0x55ecc090,
inst=..., phys_device=0x55eca990, surface_extension=...,
sur_extension_pNextChain=std::vector of length 2, capacity 2 = {...})
at vulkaninfo/vulkaninfo.h:1217
#5 0x555abeb5 in main (argc=1, argv=0x7fffde98) at
vulkaninfo/vulkaninfo.cpp:948
```
Any idea what this could be caused by? I provide core dumps if that is
helpful.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2020-09-22 (141 days ago)
InstallationMedia:
NonfreeKernelModules: nvidia_modeset nvidia
Package: nvidia-driver-460 460.39-0ubuntu1 [origin: unknown]
PackageArchitecture: amd64
ProcEnviron:
TERM=tmux-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Tags: third-party-packages hirsute wayland-session
Uname: Linux 5.10.0-14-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bumblebee sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915332/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915332] [NEW] Vulkaninfo crashes on dual gpu setup
Public bug reported:
Hi!
First, I should mention that the driver in general works very well and I
have not encountered other problems with it.
I noticed however that vulkaninfo (from vulkan-tools) is not able to
run. I think it is either related to Wayland or my prime configuration.
I tried with both XWayland and Wayland.
```
~/dev/Vulkan-Tools/build master ❯ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
ERROR at
/build/vulkan-tools-A4vpMj/vulkan-tools-1.2.162.0+dfsg1/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfaceFormats2KHR
failed with ERROR_INITIALIZATION_FAILED
~/dev/Vulkan-Tools/build master ❯ env DISPLAY= vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
'DISPLAY' environment variable not set... skipping surface info
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
fish: “env DISPLAY= vulkaninfo” terminated by signal SIGSEGV (Address boundary
error)
```
I then built vulkaninfo from source. The backtrace is not very helpful
though, it crashes somewhere inside the NVIDIA egl libraries.
```
Thread 1 "vulkaninfo" received signal SIGSEGV, Segmentation fault.
0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
(gdb) bt
#0 0x7fffed803d59 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#1 0x7fffed8041f0 in ?? () from
/lib/x86_64-linux-gnu/libnvidia-eglcore.so.460.39
#2 0x555cd723 in GetVectorInit (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 ,
init=VK_PRESENT_MODE_IMMEDIATE_KHR) at vulkaninfo/vulkaninfo.h:247
#3 0x555bcc37 in GetVector (
func_name=0x555f55e8 "vkGetPhysicalDeviceSurfacePresentModesKHR",
f=@0x7fffcfd8: 0x77833d50 )
at vulkaninfo/vulkaninfo.h:259
#4 0x555b42d5 in AppSurface::AppSurface (this=0x55ecc090,
inst=..., phys_device=0x55eca990, surface_extension=...,
sur_extension_pNextChain=std::vector of length 2, capacity 2 = {...})
at vulkaninfo/vulkaninfo.h:1217
#5 0x555abeb5 in main (argc=1, argv=0x7fffde98) at
vulkaninfo/vulkaninfo.cpp:948
```
Any idea what this could be caused by? I provide core dumps if that is helpful.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2020-09-22 (141 days ago)
InstallationMedia:
NonfreeKernelModules: nvidia_modeset nvidia
Package: nvidia-driver-460 460.39-0ubuntu1 [origin: unknown]
PackageArchitecture: amd64
ProcEnviron:
TERM=tmux-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/usr/bin/fish
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Tags: third-party-packages hirsute wayland-session
Uname: Linux 5.10.0-14-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package. Please
retry after updating the indexes of available packages, if that does not work
then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bumblebee sudo
_MarkForUpload: True
** Affects: nvidia-graphics-drivers-460 (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected hirsute third-party-packages wayland-session
** Tags added: apport-collected hirsute third-party-packages wayland-
session
** Description changed:
Hi!
First, I should mention that the driver in general works very well and I
have not encountered other problems with it.
I noticed however that vulkaninfo (from vulkan-tools) is not able to
run. I think it is either related to Wayland or my prime configuration.
I tried with both XWayland and Wayland.
```
~/dev/Vulkan-Tools/build master ❯ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_lvp.so:
wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so:
wrong ELF class: ELFCLASS32
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf_stream_paranoid=0
ERROR at
[Kernel-packages] [Bug 1915328] Re: Bionic update: upstream stable patchset 2021-02-10
Note: The following commits from v4.14.217 are being held out pending resolution of bug 1915304: 26e5eadac624 net: ipv6: Validate GSO SKB before finish IPv6 processing b26893e51f9e net: skbuff: disambiguate argument and member for skb_list_walk_safe helper 566966019ec2 net: introduce skb_list_walk_safe for skb segment walking 5440233ac430 net: use skb_list_del_init() to remove from RX sublists -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915328 Title: Bionic update: upstream stable patchset 2021-02-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-02-10 Ported from the following upstream stable releases: v4.14.216, v4.19.168, v4.19.169, v4.14.217, v4.19.170 from git://git.kernel.org/ net: cdc_ncm: correct overhead in delayed_ndp_size net: vlan: avoid leaks on register_vlan_dev() failures net: ip: always refragment ip defragmented packets net: fix pmtu check in nopmtudisc mode x86/resctrl: Use an IPI instead of task_work_add() to update PQR_ASSOC MSR x86/resctrl: Don't move a task to the same resource group vmlinux.lds.h: Add PGO and AutoFDO input sections drm/i915: Fix mismatch between misplaced vma check and vma insert spi: pxa2xx: Fix use-after-free on unbind iio: imu: st_lsm6dsx: flip irq return logic iio: imu: st_lsm6dsx: fix edge-trigger interrupts ARM: OMAP2+: omap_device: fix idling of devices during probe i2c: sprd: use a specific timeout to avoid system hang up issue cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get() spi: stm32: FIFO threshold level - fix align packet size dmaengine: xilinx_dma: check dma_async_device_register return value dmaengine: xilinx_dma: fix mixed_enum_type coverity warning wil6210: select CONFIG_CRC32 block: rsxx: select CONFIG_CRC32 iommu/intel: Fix memleak in intel_irq_remapping_alloc net/mlx5e: Fix memleak in mlx5e_create_l2_table_groups net/mlx5e: Fix two double free cases wan: ds26522: select CONFIG_BITREVERSE KVM: arm64: Don't access PMCR_EL0 when no PMU is available block: fix use-after-free in disk_part_iter_next net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet net: hns3: fix the number of queues actually used by ARQ net: stmmac: dwmac-sun8i: Balance internal PHY resource references net: stmmac: dwmac-sun8i: Balance internal PHY power net/sonic: Fix some resource leaks in error handling paths net: ipv6: fib: flush exceptions when purging route dmaengine: xilinx_dma: fix incompatible param warning in _child_probe() lightnvm: select CONFIG_CRC32 UBUNTU: upstream stable to v4.14.216, v4.19.168 ASoC: dapm: remove widget from dirty list on free MIPS: boot: Fix unaligned access with CONFIG_MIPS_RAW_APPENDED_DTB MIPS: relocatable: fix possible boot hangup with KASLR enabled ACPI: scan: Harden acpi_device_add() against device ID overflows mm/hugetlb: fix potential missing huge page size info dm snapshot: flush merged data before committing metadata r8152: Add Lenovo Powered USB-C Travel Hub ext4: fix bug for rename with RENAME_WHITEOUT ARC: build: remove non-existing bootpImage from KBUILD_IMAGE ARC: build: add uImage.lzma to the top-level target ARC: build: add boot_targets to PHONY btrfs: fix transaction leak and crash after RO remount caused by qgroup rescan ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram arch/arc: add copy_user_page() to to fix build error on ARC misdn: dsp: select CONFIG_BITREVERSE net: ethernet: fs_enet: Add missing MODULE_LICENSE ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI ARM: picoxcell: fix missing interrupt-parent properties dump_common_audit_data(): fix racy accesses to ->d_name ASoC: Intel: fix error code cnl_set_dsp_D0() NFS4: Fix use-after-free in trace_event_raw_event_nfs4_set_lock pNFS: Mark layout for return if return-on-close was not sent NFS: nfs_igrab_and_active must first reference the superblock ext4: fix superblock checksum failure when setting password salt RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp mm, slub: consider rest of partial list if acquire_slab() fails net: sunrpc: interpret the return value
[Kernel-packages] [Bug 1915328] [NEW] Bionic update: upstream stable patchset 2021-02-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-02-10 Ported from the following upstream stable releases: v4.14.216, v4.19.168, v4.19.169, v4.14.217, v4.19.170 from git://git.kernel.org/ net: cdc_ncm: correct overhead in delayed_ndp_size net: vlan: avoid leaks on register_vlan_dev() failures net: ip: always refragment ip defragmented packets net: fix pmtu check in nopmtudisc mode x86/resctrl: Use an IPI instead of task_work_add() to update PQR_ASSOC MSR x86/resctrl: Don't move a task to the same resource group vmlinux.lds.h: Add PGO and AutoFDO input sections drm/i915: Fix mismatch between misplaced vma check and vma insert spi: pxa2xx: Fix use-after-free on unbind iio: imu: st_lsm6dsx: flip irq return logic iio: imu: st_lsm6dsx: fix edge-trigger interrupts ARM: OMAP2+: omap_device: fix idling of devices during probe i2c: sprd: use a specific timeout to avoid system hang up issue cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get() spi: stm32: FIFO threshold level - fix align packet size dmaengine: xilinx_dma: check dma_async_device_register return value dmaengine: xilinx_dma: fix mixed_enum_type coverity warning wil6210: select CONFIG_CRC32 block: rsxx: select CONFIG_CRC32 iommu/intel: Fix memleak in intel_irq_remapping_alloc net/mlx5e: Fix memleak in mlx5e_create_l2_table_groups net/mlx5e: Fix two double free cases wan: ds26522: select CONFIG_BITREVERSE KVM: arm64: Don't access PMCR_EL0 when no PMU is available block: fix use-after-free in disk_part_iter_next net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet net: hns3: fix the number of queues actually used by ARQ net: stmmac: dwmac-sun8i: Balance internal PHY resource references net: stmmac: dwmac-sun8i: Balance internal PHY power net/sonic: Fix some resource leaks in error handling paths net: ipv6: fib: flush exceptions when purging route dmaengine: xilinx_dma: fix incompatible param warning in _child_probe() lightnvm: select CONFIG_CRC32 UBUNTU: upstream stable to v4.14.216, v4.19.168 ASoC: dapm: remove widget from dirty list on free MIPS: boot: Fix unaligned access with CONFIG_MIPS_RAW_APPENDED_DTB MIPS: relocatable: fix possible boot hangup with KASLR enabled ACPI: scan: Harden acpi_device_add() against device ID overflows mm/hugetlb: fix potential missing huge page size info dm snapshot: flush merged data before committing metadata r8152: Add Lenovo Powered USB-C Travel Hub ext4: fix bug for rename with RENAME_WHITEOUT ARC: build: remove non-existing bootpImage from KBUILD_IMAGE ARC: build: add uImage.lzma to the top-level target ARC: build: add boot_targets to PHONY btrfs: fix transaction leak and crash after RO remount caused by qgroup rescan ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram arch/arc: add copy_user_page() to to fix build error on ARC misdn: dsp: select CONFIG_BITREVERSE net: ethernet: fs_enet: Add missing MODULE_LICENSE ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI ARM: picoxcell: fix missing interrupt-parent properties dump_common_audit_data(): fix racy accesses to ->d_name ASoC: Intel: fix error code cnl_set_dsp_D0() NFS4: Fix use-after-free in trace_event_raw_event_nfs4_set_lock pNFS: Mark layout for return if return-on-close was not sent NFS: nfs_igrab_and_active must first reference the superblock ext4: fix superblock checksum failure when setting password salt RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp mm, slub: consider rest of partial list if acquire_slab() fails net: sunrpc: interpret the return value of kstrtou32 correctly dm: eliminate potential source of excessive kernel log noise ALSA: firewire-tascam: Fix integer overflow in midi_port_work() ALSA: fireface: Fix integer overflow in transmit_midi_msg() netfilter: conntrack: fix reading nf_conntrack_buckets usb: ohci: Make distrust_firmware param default to false nfsd4: readdirplus shouldn't return parent of export netxen_nic: fix MSI/MSI-x interrupts rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request esp: avoid unneeded kmap_atomic call net: dcb: Validate netlink message in DCB handler net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands net: stmmac: Fixed mtu channged by cache aligned net: sit: unregister_netdevice on newlink's error path net: avoid 32 x truesize under-estimation for tiny skbs rxrpc: Fix handling of an unsupported token type in rxrpc_read() tipc: fix NULL
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Few months ago I gave up and stopped using my TB18. Easier to connect few cables once a day than fight with this. I'm much happier now. TB18 serves as an expensive laptop stand for me (elevates laptop 5 cm from table). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3:
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
My keyboard just dropped out after a few hours with `5.10.0-1008-oem` build. It's working again after the unbind/bind sequence from above. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
Hi Po-Hsu,
Just reiterating that Groovy checked out fine. I did not see a proposed
kernel for Focal, even through the Bot said to try it. I get kernel
5.8.0-43 both before and after enabling proposed. Am I missing
something again, like with Bionic? It seems that regardless of the
20.04.* I install I always end up with the 5.8.0-43 kernel.
Thanks,
Tom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906128
Title:
Touchpad not detected on ByteSpeed C15B laptop
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Touchpad on a ByteSpeed C15B laptop is not working.
User will need to add i8042.noloop=1 to boot options to make it work.
[Fix]
* a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")
This fix can be cherry-picked into all affected releases.
[Test Case]
Test kernel for Bionic / Focal can be found here:
https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/
And they have been tested with positive test results.
[Where problems could occur]
The fix is just a small and simple hardware quirk. I can't think of any
potential problem for now.
== Original Bug Report ==
Touchpad hardware is OK and works for Win10. Not working for live disc, not
for 18.04 and not for 20.04 after upgrading. I've attached a Logitech wireless
mouse with its USB adapter and that works. Bluetooth is also missing, but I
have not started trying to skull that out. I'm happy to help try debugging
things, and to help resolve the issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tom1395 F pulseaudio
/dev/snd/controlC0: tom1395 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 19:09:05 2020
InstallationDate: Installed on 2020-01-26 (307 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.616
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: C15B
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ByteSpeed LLC
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: ByteSpeed Laptop C15B
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: ByteSpeed LLC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915317] [NEW] FF20.04 Fresh Install automatic update stopped wireless adapter
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 N: Unable to locate package pkgname I expected to update Nvidia 6150 Graphics Card for display compatibility Display compatible due to blacklist of nouv, wireless adapter no longer found despite being show in software additional drivers as proprietary and installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 14:32:45 2021 InstallationDate: Installed on 2021-02-09 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1915317 Title: FF20.04 Fresh Install automatic update stopped wireless adapter Status in bcmwl package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 N: Unable to locate package pkgname I expected to update Nvidia 6150 Graphics Card for display compatibility Display compatible due to blacklist of nouv, wireless adapter no longer found despite being show in software additional drivers as proprietary and installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 14:32:45 2021 InstallationDate: Installed on 2021-02-09 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1915317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
@vicamo Thanks for your explanation. I can test 5.8.0-44 as soon as it
is in proposed.
regards
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Ok, so I went back and re-read some of the most recent comments here - especially #226 and #229. This is what works for me: $ alias vmware="xmodmap -e 'remove control = Caps_Lock ' && /usr/lib/vmware/bin/vmplayer" If I start vmware with this alias, the keyboard on the host does not get corrupted when the mouse leaves the window. Well, sorta. I've used this for a few days and it was working until just now as i type this message. So this fix is not perfect. But this 2 step fix seems to get around the issue: $ setxkbmap $ alias vmware="xmodmap -e 'remove control = Caps_Lock ' To me this really looks more like a vmware bug. I plan on filing an issue there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I'm pretty confident I'm experiencing this same issue with a TB16 on "Dell Inc. XPS 15 7590/0VYV0G, BIOS 1.9.1 12/14/2020" 1. I'm able to reset my USB without unplugging/plugging with a "fix_usb" script which does: echo -n ":3a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":3a:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind 2. [ 315.161687] usb 3-1.5: 2:1: usb_set_interface failed (-19) [ 315.161727] usb 3-1.5: Not enough bandwidth for altsetting 1 I also have a Dell 9380 I've used with this dock, and I've been able to reduce the frequency of the disconnects by installing either `laptop-mode-tools` or `tlp` and setting RUNTIME_PM_DRIVER_BLACKLIST="amdgpu nouveau nvidia pcieport radeon" This forces the "MEI" device to stay "on" rather than "auto" from a PM perspective. I experience this primarily with my USB keyboard/mouse (happens with wired/wireless and Logitech/Razer). Best ways to reproduce quickly: 1. use a USB webcam, then stop using it. About 1 in 4 times this will lock up my mouse or keyboard. 2. let the computer go to display sleep and this will frequently prevent waking via the USB keyboard/mouse. I'm presently running 20.04 with linux-generic-hwe-20.04. I'm going to test the latest 5.10 as instructed above. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus
[Kernel-packages] [Bug 1915299] [NEW] nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-43-generic Date: Wed Feb 10 18:08:39 2021 Dependencies: InstallationDate: Installed on 2020-08-10 (184 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 460.39-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915299 Title: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-43-generic Date: Wed Feb 10 18:08:39 2021 Dependencies: InstallationDate: Installed on 2020-08-10 (184 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 460.39-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915145] Re: add modalias for testing
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915145 Title: add modalias for testing Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-460 source package in Focal: New Status in nvidia-graphics-drivers-460 source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Hirsute: New Bug description: nvidia-graphics-drivers-460 [Impact] * To aid installer testing of the correct kernels with/without nvidia, it would be helpful to test nvidia driver installation in qemu VMs without actually needing nvidia hardware. * We already have `Modaliases: meta(dmi:*:pnUBUNTUQEMUTEST:*)` to test installs with oem-qemu-meta (aka certified install) * It would be useful to add nvidia modalias of `dmi:*:pvrUBUNTUNVIDIATEST:*` to nvidia-graphics-drivers-460 * This way we will be able to test generic with/without nvidia; and oem with/without nvidia. By combinding pn & pvr dmi modaliases. [Test Case] * Setup ubuntu qemu libvirt vm with dmi sysinfo setting product version to UBUNTUNVIDIATEST I.e. UBUNTUNVIDIATEST ... * Boot and execute ubuntu-drivers list * Observe that nvidia drivers show up as options. [Where problems could occur] * Additional mod alias will be exposed in the package metadata, and whilst it will be installed it will not be loaded. It is purely an installer test interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915292] [NEW] Missing kernel modules when using linux-kvm
Public bug reported: Have been unable to use the linux-kvm package for our kvm virtual machines, because of missing kernel modules in the linux-modules-*-kvm package(s). The modules that has affected us for now are nfsd and tcp_bbr. Is there any reason they can't be included in the modules for linux-kvm? Or create a new linux-extra-modules-*-kvm package for those modules you deem undeserving to be in the linux-modules-*-kvm package. ** 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/1915292 Title: Missing kernel modules when using linux-kvm Status in linux-kvm package in Ubuntu: New Bug description: Have been unable to use the linux-kvm package for our kvm virtual machines, because of missing kernel modules in the linux-modules-*-kvm package(s). The modules that has affected us for now are nfsd and tcp_bbr. Is there any reason they can't be included in the modules for linux-kvm? Or create a new linux-extra-modules-*-kvm package for those modules you deem undeserving to be in the linux-modules-*-kvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1915292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462327/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462331/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462333/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462332/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462326/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462325/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462335/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462334/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462336/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462330/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462329/+files/ProcEnviron.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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462328/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462322/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462319/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462323/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462324/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462321/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462320/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags: wayland-session focal Uname: Linux 5.8.0-41-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/29/2020 dmi.bios.release: 12.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.12.00 dmi.board.name: 844F dmi.board.vendor: HP dmi.board.version: KBC Version 16.48.00 dmi.chassis.asset.tag: 5CD849CC7L dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.72 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio x360 dmi.product.name: HP ZBook Studio x360 G5 dmi.product.sku: 5LA90PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915289] [NEW] Hirsute update: v5.10.14 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.10.14 upstream stable release
from git://git.kernel.org/
Linux 5.10.14
workqueue: Restrict affinity change to rescuer
kthread: Extract KTHREAD_IS_PER_CPU
x86/cpu: Add another Alder Lake CPU to the Intel family
objtool: Don't fail the kernel build on fatal errors
habanalabs: disable FW events on device removal
habanalabs: fix backward compatibility of idle check
habanalabs: zero pci counters packet before submit to FW
drm/amd/display: Fixed corruptions on HPDRX link loss restore
drm/amd/display: Use hardware sequencer functions for PG control
drm/amd/display: Change function decide_dp_link_settings to avoid infinite
looping
drm/amd/display: Allow PSTATE chnage when no displays are enabled
drm/amd/display: Update dram_clock_change_latency for DCN2.1
selftests/powerpc: Only test lwm/stmw on big endian
platform/x86: thinkpad_acpi: Add P53/73 firmware to fan_quirk_table for dual
fan control
nvmet: set right status on error in id-ns handler
nvme-pci: allow use of cmb on v1.4 controllers
nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout
nvme-rdma: avoid request double completion for concurrent nvme_rdma_timeout
nvme: check the PRINFO bit before deciding the host buffer length
udf: fix the problem that the disc content is not displayed
i2c: tegra: Create i2c_writesl_vi() to use with VI I2C for filling TX FIFO
ALSA: hda: Add Cometlake-R PCI ID
scsi: ibmvfc: Set default timeout to avoid crash during migration
mac80211: fix encryption key selection for 802.3 xmit
mac80211: fix fast-rx encryption check
mac80211: fix incorrect strlen of .write in debugfs
objtool: Don't add empty symbols to the rbtree
ALSA: hda: Add AlderLake-P PCI ID and HDMI codec vid
ASoC: SOF: Intel: hda: Resume codec to do jack detection
scsi: fnic: Fix memleak in vnic_dev_init_devcmd2
scsi: libfc: Avoid invoking response handler twice if ep is already completed
scsi: scsi_transport_srp: Don't block target in failfast state
x86: __always_inline __{rd,wr}msr()
locking/lockdep: Avoid noinstr warning for DEBUG_LOCKDEP
habanalabs: fix dma_addr passed to dma_mmap_coherent
platform/x86: intel-vbtn: Support for tablet mode on Dell Inspiron 7352
platform/x86: touchscreen_dmi: Add swap-x-y quirk for Goodix touchscreen on
Estar Beauty HD tablet
tools/power/x86/intel-speed-select: Set higher of cpuinfo_max_freq or
base_frequency
tools/power/x86/intel-speed-select: Set scaling_max_freq to base_frequency
phy: cpcap-usb: Fix warning for missing regulator_disable
iommu/vt-d: Do not use flush-queue when caching-mode is on
ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
Revert "x86/setup: don't remove E820_TYPE_RAM for pfn 0"
arm64: Do not pass tagged addresses to __is_lm_address()
arm64: Fix kernel address detection of __is_lm_address()
arm64: dts: meson: Describe G12b GPU as coherent
drm/panfrost: Support cache-coherent integrations
iommu/io-pgtable-arm: Support coherency for Mali LPAE
ibmvnic: Ensure that CRQ entry read are correctly ordered
net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
net: dsa: bcm_sf2: put device node before return
mlxsw: spectrum_span: Do not overwrite policer configuration
stmmac: intel: Configure EHL PSE0 GbE and PSE1 GbE to 32 bits DMA addressing
net: octeontx2: Make sure the buffer is 128 byte aligned
net: fec: put child node on error path
net: stmmac: dwmac-intel-plat: remove config data on error
net: dsa: microchip: Adjust reset release timing to match reference reset
circuit
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1915289
Title:
Hirsute update: v5.10.14 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Hirsute:
Confirmed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by
[Kernel-packages] [Bug 1915264] Re: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu
apport information ** Tags added: apport-collected focal wayland-session ** Description changed: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: hrk1599 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-02-05 (5 days ago) + InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) + MachineType: HP HP ZBook Studio x360 G5 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-41-generic N/A + linux-backports-modules-5.8.0-41-generic N/A + linux-firmware1.187.9 + Tags: wayland-session focal + Uname: Linux 5.8.0-41-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/29/2020 + dmi.bios.release: 12.0 + dmi.bios.vendor: HP + dmi.bios.version: Q71 Ver. 01.12.00 + dmi.board.name: 844F + dmi.board.vendor: HP + dmi.board.version: KBC Version 16.48.00 + dmi.chassis.asset.tag: 5CD849CC7L + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 22.72 + dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.12.00:bd07/29/2020:br12.0:efr22.72:svnHP:pnHPZBookStudiox360G5:pvr:rvnHP:rn844F:rvrKBCVersion16.48.00:cvnHP:ct31:cvr: + dmi.product.family: 103C_5336AN HP ZBook Studio x360 + dmi.product.name: HP ZBook Studio x360 G5 + dmi.product.sku: 5LA90PA#ACJ + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1915264/+attachment/5462318/+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/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hrk1599 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-05 (5 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: HP HP ZBook Studio x360 G5 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=f9e396bc-107a-4b6f-80f6-8b950207e827 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.187.9 Tags:
[Kernel-packages] [Bug 1915290] [NEW] Hirsute update: v5.10.15 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.10.15 upstream stable release from git://git.kernel.org/ Linux 5.10.15 net: sched: replaced invalid qdisc tree flush helper in qdisc_replace net: dsa: mv88e6xxx: override existent unicast portvec in port_fdb_add udp: ipv4: manipulate network header of NATed UDP GRO fraglist net: ip_tunnel: fix mtu calculation neighbour: Prevent a dead entry from updating gc_list igc: Report speed and duplex as unknown when device is runtime suspended md: Set prev_flush_start and flush_bio in an atomic way Input: ili210x - implement pressure reporting for ILI251x Input: xpad - sync supported devices with fork on GitHub Input: goodix - add support for Goodix GT9286 chip x86/apic: Add extra serialization for non-serializing MSRs x86/debug: Prevent data breakpoints on cpu_dr7 x86/debug: Prevent data breakpoints on __per_cpu_offset x86/debug: Fix DR6 handling x86/build: Disable CET instrumentation in the kernel mm/filemap: add missing mem_cgroup_uncharge() to __add_to_page_cache_locked() mm: thp: fix MADV_REMOVE deadlock on shmem THP mm/vmalloc: separate put pages and flush VM flags mm, compaction: move high_pfn to the for loop scope mm: hugetlb: remove VM_BUG_ON_PAGE from page_huge_active mm: hugetlb: fix a race between isolating and freeing page mm: hugetlb: fix a race between freeing and dissolving the page mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page ARM: 9043/1: tegra: Fix misplaced tegra_uart_config in decompressor ARM: footbridge: fix dc21285 PCI configuration accessors ARM: dts; gta04: SPI panel chip select is active low DTS: ARM: gta04: remove legacy spi-cs-high to make display work again KVM: x86: Set so called 'reserved CR3 bits in LM mask' at vCPU reset KVM: x86: Update emulator context mode if SYSENTER xfers to 64-bit mode KVM: x86: fix CPUID entries returned by KVM_GET_CPUID2 ioctl KVM: x86: Allow guests to see MSR_IA32_TSX_CTRL even if tsx=off KVM: x86/mmu: Fix TDP MMU zap collapsible SPTEs KVM: SVM: Treat SVM as unsupported when running as an SEV guest nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs io_uring: don't modify identity's files uncess identity is cowed drm/amd/display: Revert "Fix EDID parsing after resume from suspend" drm/i915: Power up combo PHY lanes for for HDMI as well drm/i915: Extract intel_ddi_power_up_lanes() drm/i915/display: Prevent double YUV range correction on HDR planes drm/i915/gt: Close race between enable_breadcrumbs and cancel_breadcrumbs drm/i915/gem: Drop lru bumping on display unpinning drm/i915: Fix the MST PBN divider calculation drm/dp/mst: Export drm_dp_get_vc_payload_bw() Fix unsynchronized access to sev members through svm_register_enc_region mmc: core: Limit retries when analyse of SDIO tuples fails mmc: sdhci-pltfm: Fix linking err for sdhci-brcmstb smb3: fix crediting for compounding when only one request in flight smb3: Fix out-of-bounds bug in SMB2_negotiate() iommu: Check dev->iommu in dev_iommu_priv_get() before dereferencing it cifs: report error instead of invalid when revalidating a dentry fails RISC-V: Define MAXPHYSMEM_1GB only for RV32 xhci: fix bounce buffer usage for non-sg list case scripts: use pkg-config to locate libcrypto genirq/msi: Activate Multi-MSI early when MSI_FLAG_ACTIVATE_EARLY is set genirq: Prevent [devm_]irq_alloc_desc from returning irq 0 libnvdimm/dimm: Avoid race between probe and available_slots_show() libnvdimm/namespace: Fix visibility of namespace resource attribute tracepoint: Fix race between tracing and removing tracepoint tracing: Use pause-on-trace with the latency tracers kretprobe: Avoid re-registration of the same kretprobe earlier tracing/kprobe: Fix to support kretprobe events on unloaded modules fgraph: Initialize tracing_graph_pause at task creation gpiolib: free device name on error path to fix kmemleak mac80211: fix station rate table updates on assoc ovl: implement volatile-specific fsync error behaviour ovl: avoid deadlock on directory ioctl ovl: fix dentry leak in ovl_get_redirect thunderbolt: Fix possible NULL pointer dereference in tb_acpi_add_link() kbuild: fix duplicated flags in DEBUG_CFLAGS memblock: do not start bottom-up allocations with kernel_end vdpa/mlx5: Restore the hardware used index after change map nvmet-tcp: fix out-of-bounds access when receiving multiple h2cdata PDUs ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode net: ipa: pass correct dma_handle to dma_free_coherent() r8169: fix WoL on shutdown if CONFIG_DEBUG_SHIRQ is set net: mvpp2: TCAM entry enable should be
[Kernel-packages] [Bug 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source
The issue is still here, I'm on 20.04 and kernel 5.10 The issue goes away after a reboot, then comes back randomly. It could come back on the same day, or take a month, it's impossible to detect a pattern. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777238 Title: video lag - Every 5 seconds a freeze frame when playing video of any source Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915145] Re: add modalias for testing
** Description changed: nvidia-graphics-drivers-460 [Impact] * To aid installer testing of the correct kernels with/without nvidia, it would be helpful to test nvidia driver installation in qemu VMs without actually needing nvidia hardware. * We already have `Modaliases: meta(dmi:*:pnUBUNTUQEMUTEST:*)` to test installs with oem-qemu-meta (aka certified install) * It would be useful to add nvidia modalias of `dmi:*:pvrUBUNTUNVIDIATEST:*` to nvidia-graphics-drivers-460 * This way we will be able to test generic with/without nvidia; and oem with/without nvidia. By combinding pn & pvr dmi modaliases. [Test Case] - * Setup ubuntu qemu libvirt vm with dmi sysinfo setting product version - to UBUNTUNVIDIATEST + * Setup ubuntu qemu libvirt vm with dmi sysinfo setting product version to UBUNTUNVIDIATEST + I.e. + + + UBUNTUNVIDIATEST + + + + ... + + * Boot and execute ubuntu-drivers list * Observe that nvidia drivers show up as options. [Where problems could occur] * Additional mod alias will be exposed in the package metadata, and whilst it will be installed it will not be loaded. It is purely an installer test interface. ** Patch added: "testing-modalias.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915145/+attachment/5462268/+files/testing-modalias.patch ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915145 Title: add modalias for testing Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-460 source package in Focal: New Status in nvidia-graphics-drivers-460 source package in Groovy: New Status in nvidia-graphics-drivers-460 source package in Hirsute: New Bug description: nvidia-graphics-drivers-460 [Impact] * To aid installer testing of the correct kernels with/without nvidia, it would be helpful to test nvidia driver installation in qemu VMs without actually needing nvidia hardware. * We already have `Modaliases: meta(dmi:*:pnUBUNTUQEMUTEST:*)` to test installs with oem-qemu-meta (aka certified install) * It would be useful to add nvidia modalias of `dmi:*:pvrUBUNTUNVIDIATEST:*` to nvidia-graphics-drivers-460 * This way we will be able to test generic with/without nvidia; and oem with/without nvidia. By combinding pn & pvr dmi modaliases. [Test Case] * Setup ubuntu qemu libvirt vm with dmi sysinfo setting product version to UBUNTUNVIDIATEST I.e. UBUNTUNVIDIATEST ... * Boot and execute ubuntu-drivers list * Observe that nvidia drivers show up as options. [Where problems could occur] * Additional mod alias will be exposed in the package metadata, and whilst it will be installed it will not be loaded. It is purely an installer test interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915276] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915276 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I have recently switched to Ubuntu from Windows 10 but during and after the installation the touchpad is unresponsive at all. I have tried almost all the things from google but nothing works. I hope this issue might get resolved soon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neutrino 1440 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:16:29 2021 InstallationDate: Installed on 2021-02-10 (0 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 003: ID 5986:1135 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=e14254b4-ac0f-4e72-8e11-a450ac37103c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-10 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification Fix=== [Impact] Some ThinkPads failed to suspend to s2idle when ethernet disconnected. [Fix] I219 chip of some platforms is controlled by ME, which needs more time when setting ULP mode. Wait for ME to finish setting ULP mode. [Test] Verified on hw, and user reported s2idle works. [Regression Potential] Low, Increase timeout and breaks with condition, no impacts for who don't need this long wait. Bionic doesn't introduce the commit f15bb6dde738cc8fa0, no need for this. === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [
[Kernel-packages] [Bug 1915276] [NEW] Touchpad not working
Public bug reported: I have recently switched to Ubuntu from Windows 10 but during and after the installation the touchpad is unresponsive at all. I have tried almost all the things from google but nothing works. I hope this issue might get resolved soon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neutrino 1440 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:16:29 2021 InstallationDate: Installed on 2021-02-10 (0 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 003: ID 5986:1135 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=e14254b4-ac0f-4e72-8e11-a450ac37103c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-10 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915276 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I have recently switched to Ubuntu from Windows 10 but during and after the installation the touchpad is unresponsive at all. I have tried almost all the things from google but nothing works. I hope this issue might get resolved soon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-65-generic 5.4.0-65.73 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neutrino 1440 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 19:16:29 2021 InstallationDate: Installed on 2021-02-10 (0 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 003: ID 5986:1135 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0250:3412 Genius Wireless Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic root=UUID=e14254b4-ac0f-4e72-8e11-a450ac37103c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-10 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915276/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable
*** This bug is a duplicate of bug 1873895 *** https://bugs.launchpad.net/bugs/1873895 Same bug Lenovo Ideapad L340-15API lenovo descripción: Notebook producto: 81LW (LENOVO_MT_81LW_BU_idea_FM_IdeaPad L340-15API) fabricante: LENOVO versión: Lenovo IdeaPad L340-15API serie: PF1M98F3 anchura: 64 bits capacidades: smbios-3.1.1 dmi-3.1.1 smp vsyscall32 configuración: administrator_password=disabled boot=normal chassis=notebook family=IdeaPad L340-15API frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=LENOVO_MT_81LW_BU_idea_FM_IdeaPad L340-15API uuid=DAB52CE6-2342-E911-A225-E86A64D1E6A9 *-core descripción: Placa base producto: LNVNB161216 fabricante: LENOVO id físico: 0 versión: SDK0J40700WIN serie: PF1M98F3 ranura: Chassis Location Unknown *-memory descripción: Memoria de sistema id físico: 1 ranura: Placa de sistema o placa base tamaño: 8GiB *-bank descripción: SODIMM DDR4 Síncrono Unbuffered (Unregistered) 2400 MHz (0,4 ns) producto: 8ATF1G64HZ-2G6E1 fabricante: Micron Technology id físico: 0 serie: 2099572F ranura: DIMM 0 tamaño: 8GiB anchura: 64 bits reloj: 2400MHz (0.4ns) *-cache:0 descripción: L1 caché id físico: 3 ranura: L1 - Cache tamaño: 192KiB capacidad: 192KiB reloj: 1GHz (1.0ns) capacidades: pipeline-burst internal write-back unified configuración: level=1 *-cache:1 descripción: L2 caché id físico: 4 ranura: L2 - Cache tamaño: 1MiB capacidad: 1MiB reloj: 1GHz (1.0ns) capacidades: pipeline-burst internal write-back unified configuración: level=2 *-cache:2 descripción: L3 caché id físico: 5 ranura: L3 - Cache tamaño: 4MiB capacidad: 4MiB reloj: 1GHz (1.0ns) capacidades: pipeline-burst internal write-back unified configuración: level=3 *-cpu descripción: CPU producto: AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx fabricante: Advanced Micro Devices [AMD] id físico: 6 información del bus: cpu@0 versión: AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx serie: Unknown ranura: FP5 tamaño: 1261MHz capacidad: 3500MHz anchura: 64 bits reloj: 100MHz capacidades: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq configuración: cores=2 enabledcores=2 threads=4 *-firmware descripción: BIOS fabricante: LENOVO id físico: a versión: ARCN34WW date: 06/03/2020 tamaño: 128KiB capacidad: 8MiB capacidades: pci upgrade shadowing cdboot bootselect edd int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification netboot uefi *-pci:0 descripción: Host bridge producto: Raven/Raven2 Root Complex fabricante: Advanced Micro Devices, Inc. [AMD] id físico: 100 información del bus: pci@:00:00.0 versión: 00 anchura: 32 bits reloj: 33MHz *-generic NO RECLAMADO descripción: IOMMU producto: Raven/Raven2 IOMMU fabricante: Advanced Micro Devices, Inc. [AMD] id físico: 0.2 información del bus: pci@:00:00.2 versión: 00 anchura: 32 bits reloj: 33MHz capacidades: msi ht bus_master cap_list configuración: latency=0 *-pci:0 descripción: PCI bridge producto: Raven/Raven2 PCIe GPP Bridge [6:0] fabricante: Advanced Micro Devices, Inc. [AMD] id físico: 1.2 información del bus: pci@:00:01.2 versión: 00 anchura: 32 bits reloj:
[Kernel-packages] [Bug 1915264] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1915264 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: Incomplete Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] Re: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu
Add linux package ** Package changed: ubuntu => linux (Ubuntu) ** Tags added: suspend-resume ** Description changed: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. - System Information - + System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ - OS Information - + OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915264 Title: ALS (Ambient Light Sensor) wakes up the suspended Ubuntu Status in linux package in Ubuntu: New Bug description: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915268] [NEW] Edimax EW-7811Un V2 Wifi Dongle not supported
Public bug reported: The Edimax EW-7811Un V2 Wifi Dongle is not supported in ubuntu- raspi2-5.3 Is it possible to consider the integration of this out_of_kernel_tree driver https://github.com/lwfinger/rtl8188eu/tree/master in one of the next releases? We specifically need to use the Edimax EW-7811Un V2 in ap (a.k.a. hotspot) mode. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1915268 Title: Edimax EW-7811Un V2 Wifi Dongle not supported Status in linux-raspi package in Ubuntu: New Bug description: The Edimax EW-7811Un V2 Wifi Dongle is not supported in ubuntu- raspi2-5.3 Is it possible to consider the integration of this out_of_kernel_tree driver https://github.com/lwfinger/rtl8188eu/tree/master in one of the next releases? We specifically need to use the Edimax EW-7811Un V2 in ap (a.k.a. hotspot) mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1915268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915264] [NEW] ALS (Ambient Light Sensor) wakes up the suspended Ubuntu
You have been subscribed to a public bug: After suspending the Laptop, ALS (Ambient Light Sensor) is waking it up. System Information - Product Name: HP ZBook Studio x360 G5 SKU Number: 5LA90PA#ACJ OS Information - > uname -a Linux *** 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 I am able to disable ALS as follow - > sudo modprobe -rv hid_sensor_als modprobe: FATAL: Module hid_sensor_als is in use. So, I blaclisted hid-sensor-als by appending following text in /etc/modprobe.d/blacklist.conf - # ALS blacklist hid-sensor-als Restarted the system and checked if the module is really blacklisted using - > lsmod | grep hid_sensor_als But the issue still persists that ALS wakes up the suspended Ubuntu. Also, BIOS doesn't have the option to disable ALS. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ALS (Ambient Light Sensor) wakes up the suspended Ubuntu https://bugs.launchpad.net/bugs/1915264 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Can someone tell by when 5.8.0-44 will be released?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem remains, my environment: - Kernel: 5.4.0-65-generic - OS: Ubuntu 20.04.2 LTS - Machine: Dell Precision 5550 - Headset: Jabra Evolve 75 Couple of users facing the same issue here. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912960] Re: kcryptd, big file copy, system became unresponsive
Same problems with 5.11rc4 - seems like linux kernel issue when dm-crypt used. I suspect because of best performance. But in my case, and probably most GUI users, disk performance isn't most important. Today it is funny, can't run compilation in case I know will have Teams telco soon :) Do we know which linux mailing group handle dm-crypt issues? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912960 Title: kcryptd, big file copy, system became unresponsive Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.4 Linux eb850 5.4.0-62-generic #70-Ubuntu SMP Tue Jan 12 12:45:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Simple copy big file: janusz@eb850:~$ ls -al tmp.tar.gz -rw-r--r-- 1 janusz janusz 3847997532 sty 24 20:09 tmp.tar.gz janusz@eb850:~$ cp tmp.tar.gz tmp2.tar.gz GUI apps became unresponsive - slack/teams/firefox ... Top show all CPU (cores) ~100% usage in WA (io and kcryptd). nvme0n1 259:00 465,8G 0 disk ├─nvme0n1p1 259:10 512M 0 part /boot/efi ├─nvme0n1p2 259:20 732M 0 part /boot └─nvme0n1p3 259:30 464,6G 0 part └─nvme0n1p3_crypt 253:00 464,6G 0 crypt ├─ubuntu--vg-root 253:10 463,6G 0 lvm / └─ubuntu--vg-swap_1 253:20 980M 0 lvm [SWAP] Is there any option that will change/tune kcryptd (dm-crypt) to not use all cores? Today any operation like cp/zip/unzip/git with large files, couse I can't use ubuntu at all. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: janusz 1801 F pulseaudio /dev/snd/pcmC0D0p: janusz 1801 F...m pulseaudio /dev/snd/pcmC0D6c: janusz 1801 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-30 (269 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: HP HP EliteBook 850 G6 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash elevator=mq-deadline vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-62-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-10-31 (85 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2020 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.04.05 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.59.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR70Ver.01.04.05:bd02/18/2020:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.59.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 6XD81EA#AKD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915026] Re: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process
You will need to download all of these files (for example): https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/amd64/linux- headers-5.4.96-050496-generic_5.4.96-050496.202102071034_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/amd64/linux- headers-5.4.96-050496_5.4.96-050496.202102071034_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/amd64/linux- image- unsigned-5.4.96-050496-generic_5.4.96-050496.202102071034_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/amd64/linux- modules-5.4.96-050496-generic_5.4.96-050496.202102071034_amd64.deb and then install them together: sudo dpkg -i *.deb When rebooting, the system will still choose the higher version number which is 5.8 and not 5.4. In order to boot version 5.4 you will also need to press 'Esc' (quickly) before Ubuntu boots and select the 5.4 kernel from the boot menu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process Status in linux package in Ubuntu: Incomplete Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name 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.8.0-41-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-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/linux/+bug/1915026/+subscriptions -- Mailing list: https://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 1915026] Re: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process
Ma version actuelle obtenue avec uname -a est: Linux ubuntu-20 5.8.0-43-generic #49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux J'ai téléchargé les deux noyaux mais il est impossible de les installer. Le message d'erreur est: The following pakage have unmet dependencies Comment faire? Le mer. 10 févr. 2021 à 09:50, Daniel van Vugt <1915...@bugs.launchpad.net> a écrit : > Generic please. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915026 > > Title: > [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Bug constaté lorsque firefox est ouvert. Une partie de l'écran > sautille, la souris est mobile mais ne contrôle plus rien, plus aucun > clic actif. Le clavier reste opérationnel et me permet d'ouvrir une > console pour fermer firefox. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-41-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Feb 8 15:55:34 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] > (rev 02) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics > Controller [1043:81ea] > InstallationDate: Installed on 2021-02-06 (1 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: System manufacturer System Product Name > 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.8.0-41-generic > root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/22/2007 > dmi.bios.release: 8.12 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 0510 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: P5B-VM > dmi.board.vendor: ASUSTeK Computer INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Chassis Manufacture > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: To Be Filled By O.E.M. > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-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/linux/+bug/1915026/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process Status in linux package in Ubuntu: Incomplete Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal
[Kernel-packages] [Bug 1915246] [NEW] nvidia soft lockup after blanking
Public bug reported: X11 desktop freezes sporadic and quite frequently (about every other day). I assume it's related to the nvidia driver. An other system with same setup and AMD graphics works stable. ssh remote login and reboot is still possible. I've attached also a dmesg directly after the freeze happened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460 460.32.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 10 09:07:10 2021 InstallationDate: Installed on 2020-12-02 (70 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1915246/+attachment/5462185/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915246 Title: nvidia soft lockup after blanking Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: X11 desktop freezes sporadic and quite frequently (about every other day). I assume it's related to the nvidia driver. An other system with same setup and AMD graphics works stable. ssh remote login and reboot is still possible. I've attached also a dmesg directly after the freeze happened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460 460.32.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Feb 10 09:07:10 2021 InstallationDate: Installed on 2020-12-02 (70 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom
[Summary] MIR Team Ack under the constraint to implement the all Required (and as much Recommended as possible) of the lists below. This does need a security review, so I'll assign ubuntu-security List of specific binary packages to be promoted to main: libflashrom1 Required TODOs: - src:libftdi1 is required as well, adding a task and assigning mclemenceau to decide if he wants to own that as well. - Future owners (=Foundation) needs to check the interaction with fwupd if that is safe to not trigger any of the flashrom warnings to brick laptops. => https://flashrom.org/Laptops Once you have taken an explicit look at that please state here that it was functionally reviewed and considered safe. - get the existing self-tests in play at build time. We can't set up VMs for flash emulation in autopkgtests - but the build time tests that exist should be added to the meson build. Or dh_auto_test runs partially on makefiles? => https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/comments/3 Recommended TODOs: - this is no 1.0 so maybe one should acknowledge that stability. Please consider dropping the commandline syntax change warning fromt he man page as well as think about adding a .symbols file to auto-detect API breakage. [Duplication] There is no other package in main providing the same functionality. There is ftdi-eeprom and xc3sprog, but both cover smaller subsets of use-cases and both are not in main. But ftdi-eeprom will come back below. [Dependencies] OK: - There is a -dev which will be auto-promoted, but it brings in no further dependencies on top of what we need anyway. Problems: - other Dependencies to MIR due to this. "flashrom" as well as "libflashrom1" depend on src:libftdi1 this will have to be owned/prepared/reviewed as well to be able to complete this promotion of src:flashrom. [Embedded sources and static linking] OK: - no embedded source present - no static linking [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) Problems: - does parse data formats - does process arbitrary web content (depending on where you get your rom files) For both issues it is more the permission level of such roms that makes them security relevant. If one can sneak in odd code into the early boot that is potentially later undetectable. Also while gladly not a daemon, executing this will run at the highest possible permissions as those are needed to program the hardware. [Common blockers] OK: - does not FTBFS currently - The package has an intended team bug subscriber - no translation present, but none needed for this case (user visible)? - not a python/go package, no extra constraints to consider in that regard Problems: - does not have a test suite that runs at build time - does not have a test suite that runs as autopkgtest Here as outlined by Carl-Daniel it might need some dev effort to leverage the existing self-tests in meson build. Totally without testing this feels a bit too powerful. => https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/comments/3 [Packaging red flags] OK: - Ubuntu does not carry a delta - d/watch is present and looks ok - Upstream update history is slow but ok - Debian/Ubuntu update history is ok - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - Does not have Built-Using Problems: - symbols tracking is not in place [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf (as far as I can check it) - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu or Upstream - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks Problems: - the Readme and man page is full of warnings how destructive this can be on laptops that interact badliy with an embedded controller. It goes through some lengths to detect laptop environments and NOT run there unless the user forces it. But this MIR was requested to extend "fwupd" which myself and thousands of other users use for exactly that - keeping laptop firmware up to date. I'd want the future package owner to take a deeper look and ensure that we don't need further extra protection from bricking users by accident. - Another warning there is about the commandline syntax before 1.0. We are on 1.2 now, maybe time to drop this statement and consider things stable now? ** Also affects: libftdi (Ubuntu) Importance: Undecided Status: New ** Changed in: flashrom (Ubuntu)
[Kernel-packages] [Bug 1915026] Re: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process
Generic please. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process Status in linux package in Ubuntu: Incomplete Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name 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.8.0-41-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-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/linux/+bug/1915026/+subscriptions -- Mailing list: https://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 1915026] Re: Souris inactive et écran figé
Bonjour, Quelle version prendre, generic ou autre? Merci. Le mer. 10 févr. 2021 à 03:20, Daniel van Vugt <1915...@bugs.launchpad.net> a écrit : > Thanks. This looks like the problem: > > févr. 09 16:16:03 ubuntu-20 kernel: i915 :00:02.0: [drm] GPU HANG: > ecode 4:1:eee5fad6, in gnome-shell [2402] > févr. 09 16:16:03 ubuntu-20 kernel: i915 :00:02.0: [drm] Resetting > chip for stopped heartbeat on rcs0 > févr. 09 16:16:03 ubuntu-20 kernel: i915 :00:02.0: [drm] > gnome-shell[2402] context reset due to GPU hang > > Next please try a different kernel version like: > > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/ > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.14/ > > and tell us which versions have the bug. > > > > ** Summary changed: > > - Souris inactive et écran figé > + [i915] [Intel 965] Souris inactive et écran figé > > ** Summary changed: > > - [i915] [Intel 965] Souris inactive et écran figé > + [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process > > ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915026 > > Title: > [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Bug constaté lorsque firefox est ouvert. Une partie de l'écran > sautille, la souris est mobile mais ne contrôle plus rien, plus aucun > clic actif. Le clavier reste opérationnel et me permet d'ouvrir une > console pour fermer firefox. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-41-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Feb 8 15:55:34 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] > (rev 02) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics > Controller [1043:81ea] > InstallationDate: Installed on 2021-02-06 (1 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: System manufacturer System Product Name > 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.8.0-41-generic > root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/22/2007 > dmi.bios.release: 8.12 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 0510 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: P5B-VM > dmi.board.vendor: ASUSTeK Computer INC. > dmi.board.version: Rev 1.xx > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Chassis Manufacture > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: To Be Filled By O.E.M. > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-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/linux/+bug/1915026/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: [i915] [Intel 965] Kernel GPU hang affecting the gnome-shell process Status in linux package in Ubuntu: Incomplete Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est
