[Kernel-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Thanks. It looks like there's a basic texturing problem in OpenGL. Since that's done entirely in software for VMs, this should be assigned either to Mesa or to Cinnamon itself. I don't think we need to involve the kernel. ** No longer affects: linux (Ubuntu) ** No longer affects: xorg-server (Ubuntu) ** Bug watch added: github.com/linuxmint/cinnamon/issues #10067 https://github.com/linuxmint/cinnamon/issues/10067 ** Bug watch added: Red Hat Bugzilla #1956512 https://bugzilla.redhat.com/show_bug.cgi?id=1956512 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in mesa package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
See attached screenshot. ** Attachment added: "Screenshot showing result after apt upgrade" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+attachment/5553494/+files/ss75.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
I've checked, and the problem is still there. The update: ~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: adobe-flashplugin libllvm11 libllvm11:i386 Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed libllvm12 libllvm12:i386 linux-headers-5.4.0-94 linux-headers-5.4.0-94-generic linux-image-5.4.0-94-generic linux-modules-5.4.0-94-generic linux-modules-extra-5.4.0-94-generic The following packages will be upgraded: libegl-mesa0 libexiv2-27 libgbm1 libgl1-mesa-dri:i386 libgl1-mesa-dri libgl1-mesa-glx:i386 libgl1-mesa-glx libglapi-mesa:i386 libglapi-mesa libglx-mesa0 libglx-mesa0:i386 liblightdm-gobject-1-0 libxatracker2 lightdm linux-generic linux-headers-generic linux-image-generic linux-libc-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-vulkan-drivers:i386 xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy xwayland 27 to upgrade, 7 to newly install, 0 to remove and 0 not to upgrade. 10 standard security updates Need to get 160 MB of archives. After this operation, 634 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/universe amd64 lightdm amd64 1.30.0-0ubuntu4~20.04.2 [144 kB] Get:2 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libegl-mesa0 amd64 21.0.3-0ubuntu0.3~20.04.5 [96.2 kB] Get:3 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgbm1 amd64 21.0.3-0ubuntu0.3~20.04.5 [28.7 kB] Get:4 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-common all 2:1.20.13-1ubuntu1~20.04.2 [26.5 kB] Get:5 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-xorg-legacy amd64 2:1.20.13-1ubuntu1~20.04.2 [32.2 kB] Get:6 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 xserver-xorg-core amd64 2:1.20.13-1ubuntu1~20.04.2 [1,339 kB] Get:7 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libllvm12 amd64 1:12.0.0-3ubuntu1~20.04.4 [18.8 MB] Get:8 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgl1-mesa-dri amd64 21.0.3-0ubuntu0.3~20.04.5 [10.5 MB] Get:9 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libgl1-mesa-dri i386 21.0.3-0ubuntu0.3~20.04.5 [10.9 MB] Get:10 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libllvm12 i386 1:12.0.0-3ubuntu1~20.04.4 [19.2 MB] Get:11 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libglx-mesa0 amd64 21.0.3-0ubuntu0.3~20.04.5 [138 kB] Get:12 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libglx-mesa0 i386 21.0.3-0ubuntu0.3~20.04.5 [146 kB] Get:13 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libglapi-mesa i386 21.0.3-0ubuntu0.3~20.04.5 [26.9 kB] Get:14 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libglapi-mesa amd64 21.0.3-0ubuntu0.3~20.04.5 [26.8 kB] Get:15 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libexiv2-27 amd64 0.27.2-8ubuntu2.7 [792 kB] Get:16 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main i386 libgl1-mesa-glx i386 21.0.3-0ubuntu0.3~20.04.5 [5,532 B] Get:17 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libgl1-mesa-glx amd64 21.0.3-0ubuntu0.3~20.04.5 [5,532 B] Get:18 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/universe amd64 liblightdm-gobject-1-0 amd64 1.30.0-0ubuntu4~20.04.2 [40.0 kB] Get:19 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 libxatracker2 amd64 21.0.3-0ubuntu0.3~20.04.5 [1,716 kB] Get:20 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 linux-modules-5.4.0-94-generic amd64 5.4.0-94.106 [14.8 MB] Get:21 http://mirror.freethought-internet.co.uk/ubuntu focal-updates/main amd64 linux-image-5.4.0-94-generic amd64 5.4.0-94.106 [10.5 MB] Get:22
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Fixed for me. 5.13.0-25-generic #26-Ubuntu SMP Fri Jan 7... works no better and no worse than 5.13.0-24 (proposed). AMD Ryzen 5 2400G with AMD Radeon(TM) Vega 11 Graphics (RAVEN, DRM 3.41.0, 5.13.0-25-generic, LLVM 12.0.1). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
Hi @dgatwood, @ja, I think we should try a test kernel with the VIA chipset changes reverted, to see if it is the commit causing you issues. I have a couple of test kernels based on 5.11.0-44-generic for Focal HWE and Hirsute, and 5.13.0-23-generic for Impish currently building, and they have the below commit reverted: commit 5caa90d5fedfcdf57a42c272896cfd0ef6b5c667 commit-upstream: 5255660b208aebfdb71d574f3952cf48392f4306 Author: Jonathan Bell Date: Fri Oct 8 12:25:44 2021 +0300 Subject: xhci: add quirk for host controllers that don't update endpoint DCS Link: https://github.com/torvalds/linux/commit/5255660b208aebfdb71d574f3952cf48392f4306 Its building in https://launchpad.net/~mruffell/+archive/ubuntu/lp1956849-test and will be ready in a few hours, although I will post proper instructions on how to install the test kernel tomorrow. I will write back once the kernels have finished building, and I have had a chance to boot test them. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: New Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
Hi Vadik, Oliver, Iestyn, The test kernel has just finished building, and is ready to test. It would be great if you could install it and let me know if it fixes the issue. The kernel is 5.13.0-23-generic, with the following commit added: commit 88a04049c08cd62e698bc1b1af2d09574b9e0aee Author: Basavaraj Natikar Date: Thu Sep 23 17:59:27 2021 +0530 Subject: HID: amd_sfh: Fix potential NULL pointer dereference Link: https://github.com/torvalds/linux/commit/88a04049c08cd62e698bc1b1af2d09574b9e0aee Please note, these test packages are NOT SUPPORTED by Canonical and are for TEST PURPOSES ONLY. ONLY install in a dedicated test environment. Instructions to install (on a Impish system): 1) sudo add-apt-repository ppa:mruffell/lp1956519-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-5.13.0-23-generic linux-modules-5.13.0-23-generic linux-modules-extra-5.13.0-23-generic linux-headers-5.13.0-23-generic 4) sudo reboot 5) uname -rv 5.13.0-23-generic #23+TEST1956519v20220112b1-Ubuntu SMP Wed Jan 12 00:24:19 UTC 20 If you are asked to abort the current kernel removal, say no. You may need to change your grub config to boot the correct kernel. You can follow these instructions to do that: https://paste.ubuntu.com/p/WGpCWTPyTj/ Please make sure the uname is correct on boot. Sometimes newer kernels get pulled in due to metapackage dependencies not liking the linux- image-unsigned package. Let me know if the kernel boots correctly and you no longer have a stacktrace in "sudo dmesg". If it works, I will submit the patch for SRU into the next kernel update. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: In Progress Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [1.359540] PGD 0 P4D 0 [1.359553] Oops: 0002 [#1] SMP NOPTI [1.359569] CPU: 0 PID: 175 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.359602] Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0623 05/13/2021 [1.359632] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.359661] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d [1.359729] RSP: 0018:bf71c099f9d8 EFLAGS: 00010246 [1.359750] RAX: RBX: RCX: [1.359777] RDX: 0020 RSI: c03cd249 RDI: a680004c [1.359804] RBP: bf71c099fa20 R08: R09: 0006 [1.359831] R10: bf71c0d0 R11: 0007 R12: 000fffe0 [1.359857] R13: 992bc3387cd8 R14: 992bc11560c8 R15: 992bc3387cd8 [1.359884] FS: 7ff0ec1a48c0() GS:992ebf60() knlGS: [1.359915] CS: 0010 DS: ES: CR0: 80050033 [1.359937] CR2: 000c CR3: 000102fd CR4: 00350ef0 [1.359964] Call Trace: [1.359976] ? __pci_set_master+0x5f/0xe0 [1.359997] amd_mp2_pci_probe+0xad/0x160 [amd_sfh] [1.360021] local_pci_probe+0x48/0x80 [1.360038] pci_device_probe+0x105/0x1c0 [1.360056] really_probe+0x24b/0x4c0 [1.360073] driver_probe_device+0xf0/0x160 [1.360091] device_driver_attach+0xab/0xb0 [1.360110] __driver_attach+0xb2/0x140 [1.360126] ? device_driver_attach+0xb0/0xb0 [1.360145] bus_for_each_dev+0x7e/0xc0 [1.360161] driver_attach+0x1e/0x20 [1.360177] bus_add_driver+0x135/0x1f0 [1.360194] driver_register+0x95/0xf0 [1.360210] ? 0xc03d2000 [1.360225] __pci_register_driver+0x57/0x60 [1.360242] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.360266] do_one_initcall+0x48/0x1d0 [1.360284] ? kmem_cache_alloc_trace+0xfb/0x240 [1.360306] do_init_module+0x62/0x290 [1.360323] load_module+0xa8f/0xb10 [1.360340] __do_sys_finit_module+0xc2/0x120 [1.360359] __x64_sys_finit_module+0x18/0x20 [1.360377] do_syscall_64+0x61/0xb0 [1.361638] ? ksys_mmap_pgoff+0x135/0x260 [1.362883] ? exit_to_user_mode_prepare+0x37/0xb0 [1.364121] ? syscall_exit_to_user_mode+0x27/0x50 [1.365343] ?
[Kernel-packages] [Bug 1957019] Re: ACPI failure on Ryzen laptops
Possible dup bug 1956519 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957019 Title: ACPI failure on Ryzen laptops Status in linux package in Ubuntu: New Bug description: I have a Ryzen 4700U laptop. I'm staying on 5.13.0-22 kernel because the -23 and -25 both have ACPI failures and will hang if you shutdown or reboot the PC. I have a DMESG log showing failures: BUG: kernel NULL pointer dereference, address: 000c #PF: supervisor write access in kernel mode [1.607078] #PF: error_code(0x0002) - not-present page [1.607081] PGD 0 P4D 0 [1.607085] Oops: 0002 [#1] SMP NOPTI [1.607088] CPU: 2 PID: 205 Comm: systemd-udevd Not tainted 5.13.0-25-generic #26~20.04.1-Ubuntu [1.607093] Hardware name: HP HP ENVY x360 Convertible 13-ay0xxx/876E, BIOS F.20 07/30/2021 [1.607096] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.607107] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 a3 06 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 70 59 [1.607111] RSP: 0018:bd1d00acb9e0 EFLAGS: 00010246 [1.607115] RAX: RBX: RCX: [1.607117] RDX: 0020 RSI: c0440249 RDI: 88e00031 [1.607120] RBP: bd1d00acba28 R08: R09: 88e00052 [1.607123] R10: 0007 R11: d00f R12: 000fffe0 [1.607125] R13: 95ae94acad98 R14: 95ae812210c8 R15: 0002 [1.607128] FS: 7fdc24e64880() GS:95b17f68() knlGS: [1.607131] CS: 0010 DS: ES: CR0: 80050033 [1.607134] CR2: 000c CR3: 00011558a000 CR4: 00350ee0 [1.607136] Call Trace: [1.607140] ? __pci_set_master+0x5f/0xe0 [1.607148] amd_mp2_pci_probe+0xa8/0x140 [amd_sfh] [1.607154] local_pci_probe+0x48/0x80 [1.607158] pci_device_probe+0x10f/0x1c0 [1.607163] really_probe+0x1dc/0x440 [1.607168] driver_probe_device+0xf0/0x160 [1.607171] device_driver_attach+0x5d/0x70 [1.607174] __driver_attach+0xb2/0x140 [1.607177] ? device_driver_attach+0x70/0x70 [1.607180] bus_for_each_dev+0x7e/0xc0 [1.607185] driver_attach+0x1e/0x20 [1.607187] bus_add_driver+0x152/0x1f0 [1.607192] driver_register+0x74/0xd0 [1.607195] ? 0xc042d000 [1.607197] __pci_register_driver+0x57/0x60 [1.607201] amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] [1.607206] do_one_initcall+0x48/0x1d0 [1.607212] ? __cond_resched+0x19/0x30 [1.607218] ? kmem_cache_alloc_trace+0x37c/0x440 [1.607224] do_init_module+0x62/0x260 [1.607228] load_module+0x125d/0x1440 [1.607233] __do_sys_finit_module+0xc2/0x120 [1.607236] ? __do_sys_finit_module+0xc2/0x120 [1.607240] __x64_sys_finit_module+0x1a/0x20 [1.607243] do_syscall_64+0x61/0xb0 [1.607249] ? do_syscall_64+0x6e/0xb0 [1.607252] ? do_syscall_64+0x6e/0xb0 [1.607255] ? exc_page_fault+0x8f/0x170 [1.607259] ? asm_exc_page_fault+0x8/0x30 [1.607263] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.607266] RIP: 0033:0x7fdc253e689d [1.607270] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48 [1.607275] RSP: 002b:7ffdbbe4f6d8 EFLAGS: 0246 ORIG_RAX: 0139 [1.607279] RAX: ffda RBX: 55ca49d610a0 RCX: 7fdc253e689d [1.607282] RDX: RSI: 7fdc252c3ded RDI: 0005 [1.607284] RBP: 0002 R08: R09: [1.607287] R10: 0005 R11: 0246 R12: 7fdc252c3ded [1.607290] R13: R14: 55ca49d70ac0 R15: 55ca49d610a0 [1.607293] Modules linked in: amd_sfh(+) xhci_pci(+) i2c_piix4(+) nvme_core(+) i2c_hid xhci_pci_renesas rtsx_pci(+) wmi(+) video(+) fjes(+) hid [1.607306] CR2: 000c [1.607309] ---[ end trace 26f62dba0942f2c8 ]--- [1.607312] RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] [1.607316] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 a3 06 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 70 59 [1.607321] RSP: 0018:bd1d00acb9e0 EFLAGS: 00010246 [1.607324] RAX: RBX: RCX: [1.607327] RDX: 0020 RSI: c0440249 RDI: 88e00031 [1.607329] RBP: bd1d00acba28 R08:
[Kernel-packages] [Bug 1950764] Re: CPU hangs with kernel versions 5.4.0-{89, 90}
[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/1950764 Title: CPU hangs with kernel versions 5.4.0-{89, 90} Status in linux package in Ubuntu: Expired Bug description: Hello, We are currently experiencing issues with kernel version 5.4.0-89 as well as 5.4.0-90 on our hardware. A bit of context: We are using Ubuntu 20.04 as a basis for mobile robots that are connected to WiFi and are expected to move. With kernels 5.4.0-89 and 5.4.0-90 we are experiencing connectivity loss to our hardware. Looking into the logs we find that apparently our CPUs hang: (Computer name redacted) Nov 09 16:38:16 * kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 23s! [wpa_supplicant:470] Nov 09 16:38:16 * kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] Nov 09 16:38:16 * kernel: Modules linked in: can_raw can xsk_diag Nov 09 16:38:16 * kernel: Modules linked in: Nov 09 16:38:16 * kernel: af_packet_diag netlink_diag Nov 09 16:38:16 * kernel: can_raw Nov 09 16:38:16 * kernel: tcp_diag udp_diag Nov 09 16:38:16 * kernel: can Nov 09 16:38:16 * kernel: raw_diag Nov 09 16:38:16 * kernel: xsk_diag Nov 09 16:38:16 * kernel: inet_diag Nov 09 16:38:16 * kernel: af_packet_diag Nov 09 16:38:16 * kernel: unix_diag nft_ct Nov 09 16:38:16 * kernel: netlink_diag Nov 09 16:38:16 * kernel: nf_tables_set Nov 09 16:38:16 * kernel: tcp_diag Nov 09 16:38:16 * kernel: ccm Nov 09 16:38:16 * kernel: udp_diag Nov 09 16:38:16 * kernel: ath9k Nov 09 16:38:16 * kernel: raw_diag Nov 09 16:38:16 * kernel: ath9k_common Nov 09 16:38:16 * kernel: inet_diag Nov 09 16:38:16 * kernel: ath9k_hw Nov 09 16:38:16 * kernel: unix_diag Nov 09 16:38:16 * kernel: ath Nov 09 16:38:16 * kernel: nft_ct Nov 09 16:38:16 * kernel: intel_rapl_msr Nov 09 16:38:16 * kernel: nf_tables_set Nov 09 16:38:16 * kernel: intel_rapl_common Nov 09 16:38:16 * kernel: ccm Nov 09 16:38:16 * kernel: x86_pkg_temp_thermal Nov 09 16:38:16 * kernel: ath9k Nov 09 16:38:16 * kernel: intel_powerclamp mei_hdcp Nov 09 16:38:16 * kernel: ath9k_common Nov 09 16:38:16 * kernel: binfmt_misc snd_hda_codec_hdmi Nov 09 16:38:16 * kernel: ath9k_hw Nov 09 16:38:16 * kernel: coretemp Nov 09 16:38:16 * kernel: ath Nov 09 16:38:16 * kernel: mac80211 snd_hda_codec_realtek Nov 09 16:38:16 * kernel: intel_rapl_msr Nov 09 16:38:16 * kernel: kvm_intel nls_iso8859_1 Nov 09 16:38:16 * kernel: intel_rapl_common Nov 09 16:38:16 * kernel: snd_hda_codec_generic ledtrig_audio Nov 09 16:38:16 * kernel: x86_pkg_temp_thermal Nov 09 16:38:16 * kernel: kvm Nov 09 16:38:16 * kernel: intel_powerclamp Nov 09 16:38:16 * kernel: advsocketcan(OE) sja1000 snd_hda_intel Nov 09 16:38:16 * kernel: mei_hdcp Nov 09 16:38:16 * kernel: snd_intel_dspcfg snd_hda_codec Nov 09 16:38:16 * kernel: binfmt_misc Nov 09 16:38:16 * kernel: rapl cfg80211 Nov 09 16:38:16 * kernel: snd_hda_codec_hdmi Nov 09 16:38:16 * kernel: intel_cstate snd_hda_core Nov 09 16:38:16 * kernel: coretemp Nov 09 16:38:16 * kernel: snd_hwdep Nov 09 16:38:16 * kernel: mac80211 Nov 09 16:38:16 * kernel: snd_pcm Nov 09 16:38:16 * kernel: snd_hda_codec_realtek kvm_intel nls_iso8859_1 Nov 09 16:38:16 * kernel: libarc4 Nov 09 16:38:16 * kernel: snd_hda_codec_generic ledtrig_audio kvm Nov 09 16:38:16 * kernel: snd_timer Nov 09 16:38:16 * kernel: advsocketcan(OE) sja1000 snd_hda_intel Nov 09 16:38:16 * kernel: serio_raw Nov 09 16:38:16 * kernel: snd_intel_dspcfg snd_hda_codec rapl Nov 09 16:38:16 * kernel: can_dev Nov 09 16:38:16 * kernel: cfg80211 intel_cstate snd_hda_core Nov 09 16:38:16 * kernel: ftdi_sio Nov 09 16:38:16 * kernel: snd_hwdep snd_pcm libarc4 Nov 09 16:38:16 * kernel: snd Nov 09 16:38:16 * kernel: snd_timer serio_raw can_dev Nov 09 16:38:16 * kernel: mei_me Nov 09 16:38:16 * kernel: ftdi_sio snd mei_me Nov 09 16:38:16 * kernel: usbserial Nov 09 16:38:16 * kernel: usbserial mei Nov 09 16:38:16 * kernel: mei Nov 09 16:38:16 * kernel: soundcore intel_pch_thermal Nov 09 16:38:16 * kernel: soundcore Nov 09 16:38:16 * kernel: acpi_pad Nov 09 16:38:16 * kernel: intel_pch_thermal Nov 09 16:38:16 * kernel: mac_hid Nov 09 16:38:16 * kernel: acpi_pad mac_hid Nov 09 16:38:16 * kernel: nft_masq Nov 09 16:38:16 * kernel: nft_masq nft_chain_nat Nov 09 16:38:16 * kernel: nft_chain_nat Nov 09 16:38:16 * kernel: nf_nat nf_conntrack nf_defrag_ipv6 Nov 09 16:38:16 * kernel: nf_nat Nov 09 16:38:16 * kernel: nf_defrag_ipv4 nf_tables Nov 09 16:38:16 * kernel: nf_conntrack Nov 09 16:38:16 * kernel: nfnetlink sch_fq_codel Nov 09 16:38:16
[Kernel-packages] [Bug 1859592] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553444/+files/acpidump.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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553433/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553437/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553443/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553434/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553441/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553440/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553442/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553438/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553439/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553435/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553432/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553436/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553430/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553431/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553429/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1859592/+attachment/5553428/+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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rashmitha 1751 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-24 (140 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. Dell KB216 Wired Keyboard Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-46-generic root=UUID=c2e675a6-0a05-4eab-90f2-87dc5a7dd094 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-46-generic N/A linux-backports-modules-5.11.0-46-generic N/A linux-firmware 1.187.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo ubridge _MarkForUpload: True dmi.bios.date: 08/31/2021 dmi.bios.release: 15.38 dmi.bios.vendor: Insyde dmi.bios.version: F.38 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8533 dmi.board.vendor: HP dmi.board.version: 70.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.38 dmi.modalias: dmi:bvnInsyde:bvrF.38:bd08/31/2021:br15.38:efr70.38:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:sku6YE09PA#ACJ:rvnHP:rn8533:rvr70.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6YE09PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Tags added: 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956519] Re: kernel panic after upgrading to kernel 5.13.0-23
FYI - still occurs in 5.13.0-25. Linux version 5.13.0-25-generic (buildd@lgw01-amd64-047) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #26-Ubuntu SMP Fri Jan 7 15:48:31 UTC 2022 BUG: kernel NULL pointer dereference, address: 000c #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI CPU: 0 PID: 191 Comm: systemd-udevd Not tainted 5.13.0-25-generic #26-Ubuntu Hardware name: ASUSTeK COMPUTER INC. MINIPC PN50/PN50, BIOS 0620 03/18/2021 RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d RSP: 0018:a431c0a2fa60 EFLAGS: 00010246 RAX: RBX: RCX: RDX: 0020 RSI: c0415249 RDI: 9560004c RBP: a431c0a2faa8 R08: R09: 0006 R10: a431c0d0 R11: 0007 R12: 000fffe0 R13: 91d1170ead98 R14: 91d1014bb0c8 R15: 91d1170ead98 FS: 7fa5fe59d8c0() GS:91d7ef60() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 000c CR3: 00011785 CR4: 00350ef0 Call Trace: ? __pci_set_master+0x5f/0xe0 amd_mp2_pci_probe+0xad/0x160 [amd_sfh] local_pci_probe+0x48/0x80 pci_device_probe+0x105/0x1c0 really_probe+0x24b/0x4c0 driver_probe_device+0xf0/0x160 device_driver_attach+0xab/0xb0 __driver_attach+0xb2/0x140 ? device_driver_attach+0xb0/0xb0 bus_for_each_dev+0x7e/0xc0 driver_attach+0x1e/0x20 bus_add_driver+0x135/0x1f0 driver_register+0x95/0xf0 ? 0xc041a000 __pci_register_driver+0x57/0x60 amd_mp2_pci_driver_init+0x23/0x1000 [amd_sfh] do_one_initcall+0x48/0x1d0 ? kmem_cache_alloc_trace+0xfb/0x240 do_init_module+0x62/0x290 load_module+0xa8f/0xb10 __do_sys_finit_module+0xc2/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x61/0xb0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x20 ? do_syscall_64+0x6e/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fa5feb3394d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc5ce60ba8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 56027b85af40 RCX: 7fa5feb3394d RDX: RSI: 7fa5fecc33fe RDI: 000c RBP: 0002 R08: R09: R10: 000c R11: 0246 R12: 7fa5fecc33fe R13: 56027b845ed0 R14: 56027b85b030 R15: 56027b84a330 Modules linked in: amd_sfh(+) i2c_hid_acpi libahci i2c_hid i2c_piix4(+) xhci_pci_renesas(+) nvme_core(+) wmi(+) video(+) fjes(+) hid CR2: 000c ---[ end trace cc368d63aaf78960 ]--- RIP: 0010:amd_sfh_hid_client_init+0x47/0x350 [amd_sfh] Code: 00 53 48 83 ec 20 48 8b 5f 08 48 8b 07 48 8d b3 22 01 00 00 4c 8d b0 c8 00 00 00 e8 23 07 00 00 45 31 c0 31 c9 ba 00 00 20 00 <89> 43 0c 48 8d 83 68 01 00 00 48 8d bb 80 01 00 00 48 c7 c6 20 6d RSP: 0018:a431c0a2fa60 EFLAGS: 00010246 RAX: RBX: RCX: RDX: 0020 RSI: c0415249 RDI: 9560004c RBP: a431c0a2faa8 R08: R09: 0006 R10: a431c0d0 R11: 0007 R12: 000fffe0 R13: 91d1170ead98 R14: 91d1014bb0c8 R15: 91d1170ead98 FS: 7fa5fe59d8c0() GS:91d7ef60() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 000c CR3: 00011785 CR4: 00350ef0 Still fails to boot (systemd-udev-settle hangs so ZFS BOOT fails to mount). Can mount ZFS BOOT manually in emergency mode (after importing the pool). But systemd does not recover complaining about a dependency cycle in its current transaction. Couldn't figure out how to resolve that... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956519 Title: kernel panic after upgrading to kernel 5.13.0-23 Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: In Progress Bug description: After upgrading my son's Asus PN50 with Ubuntu 21.10 to the latest kernel 5.13.0-23, I am no longer able to boot it normally. Kernel fails with the panic halfway through the boot process (which got overall suspiciously slow): [1.359465] BUG: kernel NULL pointer dereference, address: 000c [1.359498] #PF: supervisor write access in kernel mode [1.359519] #PF: error_code(0x0002) - not-present page [
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** No longer affects: alsa-ucm-conf (Ubuntu Focal) ** No longer affects: alsa-ucm-conf (Ubuntu Hirsute) ** No longer affects: alsa-ucm-conf (Ubuntu Impish) ** Changed in: alsa-topology-conf (Ubuntu) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: alsa-topology-conf (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-topology-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: Fix Released Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
This can be the efifb regression Linus also encountered. FWIW, the initial efifb runtime PM grabbing is written by me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 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: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Michael, Is it possible to perform git bisect to find the offending commit? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 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: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001: dmi.product.family: VMware dmi.product.name: VBSA dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Hi there, VMware here... We're able to repro this and have the following temporary workaround while we figure out who's code needs adjusting: We are able to boot by adding: acpi=force to: GRUB_CMDLINE_LINUX_DEFAULT in: /etc/default/grub Such that the full line reads: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Remember to also disable Wayland (which is not presently supported in this Fusion tech preview) in /etc/gdm3/custom.conf by uncommenting WaylandEnable=false. When it's in the unresponsive state it still boots so ssh works... you can check /proc/iomem and it seems like the PCI memory is already reserved for BOOTFB.. Not working state: 5000-7fff : pcie@0x4000 7800-7fff : :00:0f.0 7800-782f : BOOTFB Working state: (i.e. with acpi=force) 5000-7fff : PCI Bus :00 5000-501f : PCI Bus :20 5020-503f : PCI Bus :21 5040-505f : PCI Bus :21 7800-782f : BOOTFB We have an internal bug filed so I'll update if we have more we can share. Thanks, -Michael -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 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: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-intel-5.13/5.13.0.1009.10)
All autopkgtests for the newly accepted linux-meta-intel-5.13 (5.13.0.1009.10) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-intel-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
Similar issue; also Thinkpad. All USB ports break when connecting a specific USB device during runtime. If the specific device is already connected during boot, it'll work fine. uname -a Linux think 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux dpkg --list linux-firmware Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii linux-firmware 1.187.24 all Firmware for Linux kernel drivers dmesg -w [46438.144293] xhci_hcd :00:14.0: Abort failed to stop command ring: -110 [46438.144300] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [46438.144318] xhci_hcd :00:14.0: HC died; cleaning up [46438.144377] xhci_hcd :00:14.0: Timeout while waiting for setup device command [46438.144384] clocksource: timekeeping watchdog on CPU5: Marking clocksource 'tsc' as unstable because the skew is too large: [46438.144386] clocksource: 'acpi_pm' wd_now: 733873 wd_last: b63823 mask: ff [46438.144388] clocksource: 'tsc' cs_now: 542df475a1df cs_last: 542c599b562b mask: [46438.144389] tsc: Marking TSC unstable due to clocksource watchdog [46438.144400] usb 1-2: USB disconnect, device number 2 [46438.144403] usb 1-2.3: USB disconnect, device number 4 [46438.144405] usb 1-2.3.3: USB disconnect, device number 7 [46438.144406] usb 1-2.3.3.1: USB disconnect, device number 14 [46438.144607] usb 1-2.3.3.2: USB disconnect, device number 10 [46438.144845] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [46438.144846] sched_clock: Marking unstable (46438131062428, 13782220)<-(4643813798, -55148943) [46438.144884] clocksource: Checking clocksource tsc synchronization from CPU 3. [46438.144906] clocksource: Switched to clocksource acpi_pm [46438.216564] usb 1-2.3.3.3: USB disconnect, device number 11 [46438.216568] usb 1-2.3.3.3.1: USB disconnect, device number 12 [46438.481130] usb 1-2.3.3.3.2: USB disconnect, device number 13 [46438.528512] usbhid 1-2.3.3.3.2:1.0: Razer Device disconnected [46438.608575] usbhid 1-2.3.3.3.2:1.1: Razer Device disconnected [46438.720839] usbhid 1-2.3.3.3.2:1.2: Razer Device disconnected [46438.722739] usb 1-5: USB disconnect, device number 3 [46438.722974] usb 1-6: USB disconnect, device number 5 [46438.728331] usb 2-4: device not accepting address 5, error -108 [46438.728409] usb usb2-port4: couldn't allocate usb_device [46438.728428] usb 2-2: USB disconnect, device number 2 [46438.728434] usb 2-2.1: USB disconnect, device number 3 [46438.784605] usb 1-8: USB disconnect, device number 6 [46438.816916] usb 2-2.3: USB disconnect, device number 4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset
[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1009.9 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-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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-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/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Nvidia notified me via private email that they'd discovered some issues with the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch intended to resolve them. My knowledge of these changes is limited to what is mentioned in the commit message: - Allow clients to opt out of unmap during invalidation - Fix some bugs in the sequencing of mlx5 MRs - Enable ATS for peer memory [Test Case] ib_write_bw from the perftest package, rebuilt with CUDA support, can be used as a smoke test of this feature. I'll attach a sample test script here. I've verified this test passes with the kernels in the archive, and continues to pass with the provided patch applied. [Fix] Nvidia has emailed me fixes for both trees. They are not currently available in a public tree elsewhere, though I'm told at some point they should end up in a branch here: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/ [What could go wrong] The only known use case for ib_peer_memory are Nvidia GPU users making use of the GPU PeerDirect feature where GPUs can share memory with one another over an Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) with such workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1009.9 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-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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-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/1950584 Title: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] "Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the ->adjust_perf() callback") caused intel_pstate to use nonzero HWP desired values in certain usage scenarios, but it did not prevent them from being leaked into the confugirations in which HWP desired is expected to be 0" I believe I'm seeing this issue on my laptop during suspend/resume. The upstream fix is: [Fix] commit dbea75fe18f60e364de6d994fc938a24ba249d81 Author: Rafael J. Wysocki Date: Wed Nov 3 19:43:47 2021 +0100 cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cking 2316 F pulseaudio /dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio /dev/snd/controlC0: cking 2316 F pulseaudio /dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-07 (156 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607) MachineType: LENOVO 20L5CTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.202 Tags: jammy Uname: Linux 5.13.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/11/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956413] Re: Intel EHL: Two of the on-board ethernet ports don't work
This bug is awaiting verification that the linux- intel-5.13/5.13.0-1009.9 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-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. 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-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1956413 Title: Intel EHL: Two of the on-board ethernet ports don't work Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Triaged Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: == Impact == Only one of the three on-board ethernet ports works. The other two can't get IP addresses. == Fix == commit 884d2b845477cd0a18302444dc20fe2d9a01743e Author: David Wu Date: Mon Dec 13 19:15:15 2021 +0800 net: stmmac: Add GFP_DMA32 for rx buffers if no 64 capability Use page_pool_alloc_pages instead of page_pool_dev_alloc_pages, which can give the gfp parameter, in the case of not supporting 64-bit width, using 32-bit address memory can reduce a copy from swiotlb. Signed-off-by: David Wu Signed-off-by: David S. Miller == Risk of Regression == Low. The commit changes gfp parameter only when there's no 64-bit capability, and it is already in mainline. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
yes this is a real mess. @yrogge according to the kernel bot message when you removed the verification-needed-impish tag and added the verification-done-impish tag that should have been what "confirmed" the fix to be included. so please, can @arighi the bug assignee, or some other ubuntu person please fix this and get the now well-confirmed fix into a released kernel asap?? thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Issue has been resolved on AMD Ryzen 3500U as well with kernel 5.13.0-25. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
5.13.0-25 fixed for me amdgpu graphics init issue on AMD Ryzen 5 3400G. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog
This looks like the same issue as #1945011 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946828 Title: ntfsresize hang and call traces in syslog Status in linux package in Ubuntu: Confirmed Status in ntfs-3g package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in ntfs-3g source package in Jammy: Confirmed Status in ubiquity source package in Jammy: Confirmed Bug description: Attempting to boot the impish final iso on my kvm VM setup with a windows 10 install on the virtual disk. The install process hangs at the "updates and other software" screen, apparently on a ntfsresize call. Mind you, this is before I have chosen disks to partition - I'm at the step where I can choose a Normal or Minimal installation. While this is not a 100% reproduction rate issue, the rate seems high - above 50% I would guess. If I try to quickly click thru the installer on boot it might be a little more likely. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4609 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 13 02:40:56 2021 IwConfig: lono wireless extensions. enp1s0no wireless extensions. LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Hello, I updated to 5.13.0-25 and I confirm it works properly on a Ryzen 5-3600G. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Hello, thanks for the fast update. Unfortunately my personal problem isn't fixed with it. I'm using a Ryzen 7 5700U (on a hp envy x360-15eu000), with ubuntu 21.10. I use full disk encryption with luks, and when I try to boot with the new kernel (5.13.0-23, or now the newer 5.13.0-25) I type in the correct password and get stuck after this (last appearing message: [...] successfully decypted). Usually (e.g with the 5.13.0-22 kernel), after decrypting the partition the system boots up and a row of instructions appear. With this kernel(s) it's completely stuck and nothing happens. Is anyone else experiencing this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Re: webcam doesn't work
My bad. I sent logs after rolling back to the previous kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553421/+files/acpidump.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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553420/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553419/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553418/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553414/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553416/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553417/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553415/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553412/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553410/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553411/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553413/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553409/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553408/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553406/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553407/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957112] Re: webcam doesn't work
apport information ** Tags added: apport-collected una ** Description changed: - As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. - My webcam doesn't work + As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: piotr 2920 F pulseaudio + /dev/snd/controlC0: piotr 2920 F pulseaudio + /dev/snd/controlC1: piotr 2920 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + InstallationDate: Installed on 2020-06-07 (583 days ago) + InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 + IwConfig: + enp3s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-91-generic N/A + linux-backports-modules-5.4.0-91-generic N/A + linux-firmware1.187.24 + RfKill: + + Tags: una + Uname: Linux 5.4.0-91-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 10/27/2011 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F4 + dmi.board.name: H67MA-USB3-B3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: H67MA-USB3-B3 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1957112/+attachment/5553405/+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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957113] [NEW] Bionic update: upstream stable patchset 2022-01-11
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 2022-01-11 Ported from the following upstream stable releases: v4.14.258, v4.19.221 from git://git.kernel.org/ HID: add hid_is_usb() function to make it simpler for USB detection HID: add USB_HID dependancy to hid-prodikeys HID: add USB_HID dependancy to hid-chicony HID: add USB_HID dependancy on some USB HID drivers HID: wacom: fix problems when device is not a valid USB device HID: check for valid USB device for many HID drivers can: sja1000: fix use after free in ems_pcmcia_add_card() nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done bpf: Fix the off-by-two error in range markings nfp: Fix memory leak in nfp_cpp_area_cache_add() seg6: fix the iif in the IPv6 socket control block IB/hfi1: Correct guard on eager buffer deallocation mm: bdi: initialize bdi_min_ratio when bdi is unregistered ALSA: ctl: Fix copy of updated id with element read/write ALSA: pcm: oss: Fix negative period/buffer sizes ALSA: pcm: oss: Limit the period size to 16MB ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*() tracefs: Have new files inherit the ownership of their parent can: pch_can: pch_can_rx_normal: fix use after free can: m_can: Disable and ignore ELO interrupt libata: add horkage for ASMedia 1092 wait: add wake_up_pollfree() binder: use wake_up_pollfree() signalfd: use wake_up_pollfree() tracefs: Set all files to the same group ownership as the mount option block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2) qede: validate non LSO skb length net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero net: altera: set a couple error code in probe() net: fec: only clear interrupt of handling queue in fec_enet_rx_queue() net, neigh: clear whole pneigh_entry at alloc time net/qla3xxx: fix an error code in ql_adapter_up() USB: gadget: detect too-big endpoint 0 requests USB: gadget: zero allocate endpoint 0 buffers usb: core: config: fix validation of wMaxPacketValue entries xhci: Remove CONFIG_USB_DEFAULT_PERSIST to prevent xHCI from runtime suspending usb: core: config: using bit mask instead of individual bits iio: trigger: Fix reference counting iio: trigger: stm32-timer: fix MODULE_ALIAS iio: stk3310: Don't return error code in interrupt handler iio: mma8452: Fix trigger reference couting iio: ltr501: Don't return error code in trigger handler iio: kxsd9: Don't return error code in trigger handler iio: itg3200: Call iio_trigger_notify_done() on error iio: dln2-adc: Fix lockdep complaint iio: dln2: Check return value of devm_iio_trigger_register() iio: adc: axp20x_adc: fix charging current reporting on AXP22x iio: accel: kxcjk-1013: Fix possible memory leak in probe and remove irqchip/armada-370-xp: Fix return value of armada_370_xp_msi_alloc() irqchip/armada-370-xp: Fix support for Multi-MSI interrupts irqchip/irq-gic-v3-its.c: Force synchronisation when issuing INVALL irqchip: nvic: Fix offset for Interrupt Priority Offsets bonding: make tx_rebalance_counter an atomic UBUNTU: upstream stable to v4.14.258, v4.19.221 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - 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
[Kernel-packages] [Bug 1957112] [NEW] webcam doesn't work
Public bug reported: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: webcam -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: New Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I've updated to 5.13.0-25 and can confirm that this fixed the problem on my Ryzen 3700U laptop, which had been broken by the -23 kernel. Since I see some comments here talking about sleep, I tried that as well: I suspended the system and then woke it up, and I did not encounter any unusual behavior. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1
New debdiff, because v2 was missing the gcc-10 dependency for zfs-dkms in debian/control. ** Patch added: "zfs-update-to-2.1.2-v3.debdiff" https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+attachment/5553379/+files/zfs-update-to-2.1.2-v3.debdiff -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1
New debdiff in attach that enforces gcc-10 to build the dkms part on s390x. ** Description changed: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] - Temporary workaround is to downgrade gcc. + Temporary workaround is to build zfs with gcc-10 on s390x. + + [Regression potential] + + Building a kernel module with a different compiler is never 100% safe, + we may experience potential crashes / panics if the ABI is not + compatible. Moreover, if we build zfs with gcc-10 we are going to lose + some of the performance benefits provided by gcc-11. + + However these regressions are limited to zfs on s390x and without this + change zfs is broken anyway on this architecture. ** Patch added: "zfs-update-to-2.1.2-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+attachment/5553372/+files/zfs-update-to-2.1.2-v2.debdiff -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956585] Re: OOB write on BPF_RINGBUF
This was assigned CVE-2021-4204. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4204 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956585 Title: OOB write on BPF_RINGBUF Status in linux package in Ubuntu: Fix Released Bug description: tr3e wang discovered that an OOB write existed in the eBPF subsystem in the Linux kernel on BPF_RINGBUF. Mitigation commit: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/commit/?id=53fb7741ff9d546174dbb585957b4f8b6afbdb83 Mitigation: Disable unprivileged ebpf with: $ sudo sysctl kernel.unprivileged_bpf_disabled=1 Unprivileged ebpf is disabled by default in Ubuntu 21.10 and newer. See https://www.kernel.org/doc/html/latest/admin- guide/sysctl/kernel.html#unprivileged-bpf-disabled for details on the configuration setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown
Can confirm yes also -25 Kernel on Asus PN-50 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic, the system cannot be powered down or rebooted, just hangs indefinitely. A screenshot with the final screen is shown here: https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff I can restore the previous behavior (i.e. a correct shutdown) with choosing the previous kernel in the grub menu on boot. Is there anything I can do to provide more information and debug this further? My system information: Description: Ubuntu 21.10 Release: 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petr 1146 F pulseaudio /dev/snd/controlC0: petr 1146 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-07 (62 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgxubuntu-root ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 04/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957018] Re: System hangs on reboot and shutdown
Same issue here on Asus PN50 Ryzen 5 4500U Bios 0623 Also with 5.13.0-23-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957018 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-25-generic, the system cannot be powered down or rebooted, just hangs indefinitely. This is a possible duplicate of the link below https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957018] Re: System hangs on reboot and shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1957018 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-25-generic, the system cannot be powered down or rebooted, just hangs indefinitely. This is a possible duplicate of the link below https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957090] [NEW] some times the screen will be no response, even keyboard and mouse.
Public bug reported: some times the screen will be no response , even keyboard and mouse. Every thing is died. I have to mandatory shutdown to recover my computer. The frequency is about once every two days. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 23:02:11 2022 InstallationDate: Installed on 2020-10-01 (466 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: crash UpgradeStatus: Upgraded to jammy on 2021-12-26 (16 days ago) ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1957090 Title: some times the screen will be no response,even keyboard and mouse. Status in crash package in Ubuntu: New Bug description: some times the screen will be no response , even keyboard and mouse. Every thing is died. I have to mandatory shutdown to recover my computer. The frequency is about once every two days. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 23:02:11 2022 InstallationDate: Installed on 2020-10-01 (466 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: crash UpgradeStatus: Upgraded to jammy on 2021-12-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1957090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957091] Re: some times the screen will be no response, even keyboard and mouse.
journalctl log ** Attachment added: "die4.log" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1957091/+attachment/5553366/+files/die4.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1957091 Title: some times the screen will be no response,even keyboard and mouse. Status in crash package in Ubuntu: New Bug description: some times the screen will be no response , even keyboard and mouse. Every thing is died. I have to mandatory shutdown to recover my computer. The frequency is about once every two days. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 23:02:11 2022 InstallationDate: Installed on 2020-10-01 (466 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: crash UpgradeStatus: Upgraded to jammy on 2021-12-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1957091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957091] [NEW] some times the screen will be no response, even keyboard and mouse.
Public bug reported: some times the screen will be no response , even keyboard and mouse. Every thing is died. I have to mandatory shutdown to recover my computer. The frequency is about once every two days. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 23:02:11 2022 InstallationDate: Installed on 2020-10-01 (466 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: crash UpgradeStatus: Upgraded to jammy on 2021-12-26 (16 days ago) ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1957091 Title: some times the screen will be no response,even keyboard and mouse. Status in crash package in Ubuntu: New Bug description: some times the screen will be no response , even keyboard and mouse. Every thing is died. I have to mandatory shutdown to recover my computer. The frequency is about once every two days. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: crash (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 11 23:02:11 2022 InstallationDate: Installed on 2020-10-01 (466 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: crash UpgradeStatus: Upgraded to jammy on 2021-12-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1957091/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@aronovitch: Thanks for your explanation. I hope that somebody will confirm the patch with the correct privileges before -26 freeze. Maybe there is some rule as "ThinkPad users have to use only even versions, never odd ones" ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Just Updated to 5.13.0-25-generic, it seems to be fixed, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956821] Re: System hangs on reboot and shutdown
Still present on latest -25 kernel on an ASUS PN-50 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956821 Title: System hangs on reboot and shutdown Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from kernel 5.13.0-22-generic to 5.13.0-23-generic, the system cannot be powered down or rebooted, just hangs indefinitely. A screenshot with the final screen is shown here: https://askubuntu.com/questions/1385794/system-hangs-on-reboot-and-poweroff I can restore the previous behavior (i.e. a correct shutdown) with choosing the previous kernel in the grub menu on boot. Is there anything I can do to provide more information and debug this further? My system information: Description: Ubuntu 21.10 Release: 21.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: petr 1146 F pulseaudio /dev/snd/controlC0: petr 1146 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-11-07 (62 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20YA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgxubuntu-root ro ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-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: 04/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: GMCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G3 ACN dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrGMCN21WW:bd04/07/2021:br1.21:efr1.16:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN: dmi.product.family: ThinkBook 13s G3 ACN dmi.product.name: 20YA dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN dmi.product.version: ThinkBook 13s G3 ACN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956821/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Jammy will release a few months later and we are aware of the development activities of Jammy 5.15 kernel. The patch needs to land Jammy as well to prevent user's dist-upgrade regression. My investigation of the patch, 183b60e00597 crypto: hisilicon/qm - modify the uacce mode check, has clean cherry-pick with Jammy 5.15 master-next, and fixes the issue[1]. Next: Process to merge 183b60e00597 with Jammy 5.15 kernel along with impish 5.13 (for up-coming focal-hwe) [1] Before applying the patch (master-next branch, 5.15.13): ubuntu@segers:~$ sudo ./collect.sh Linux segers 5.15.0-16-generic #16~d20220111t131721~7ec137fc2603 SMP Tue Jan 11 13:18:16 UTC 20 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal [3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 13.974371] dw_spi_mmio HISI0173:00: DMA init failed [ 19.448332] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 19.820834] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 19.852904] sas: Enter sas_scsi_recover_host busy: 0 failed: 0 [ 20.224761] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 [ 22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 22.982319] hisi_sec2 :75:00.0: fail to alloc uacce (-22) [ 22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.14] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 23.010710] hisi_sec2 :b5:00.0: fail to alloc uacce (-22) == [0.00] cma: Reserved 32 MiB at 0x7e00 [0.00] Memory: 131307604K/134213440K available (17280K kernel code, 4572K rwdata, 13820K rodata, 9600K init, 1182K bss, 2873068K reserved, 32768K cma-reserved) [3.408872] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.594241] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.636486] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.678612] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.720721] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.762846] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.805032] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.847216] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.889401] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.970515] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 12.067413] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.956757] cma_alloc: 10 callbacks suppressed [ 22.956763] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.966698] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 [ 22.990846] cma: cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12 [ 22.14] cma: cma_alloc: reserved: alloc failed, req-size: 16 pages, ret: -12 == == [ 22.982319] hisi_sec2 :75:00.0: fail to alloc uacce (-22) [ 23.010710] hisi_sec2 :b5:00.0: fail to alloc uacce (-22) == == == After apply the patch: ubuntu@segers:~$ sudo ./collect.sh Linux segers 5.15.0-16-generic #16~d20220111t123224~c7a448651f57 SMP Tue Jan 11 12:33:20 UTC 20 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal [3.409019] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 [ 11.604567] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [ 11.646821] cma: cma_alloc: reserved: alloc failed, req-size: 256 pages, ret: -12 [
[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
** Also affects: kunpeng920/ubuntu-22.04 Importance: Undecided Status: New ** Changed in: kunpeng920/ubuntu-21.10 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-22.04 Status: New => In Progress ** Changed in: kunpeng920/ubuntu-21.10 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) ** Changed in: kunpeng920/ubuntu-22.04 Assignee: (unassigned) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: In Progress Status in kunpeng920 ubuntu-21.10 series: In Progress Status in kunpeng920 ubuntu-22.04 series: In Progress Status in linux package in Ubuntu: New Status in linux source package in Impish: In Progress Status in linux source package in Jammy: New Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Hi everyone, small progress report : I tried the pipewire trick and it didn't work out for me, while it initially seemed to work: auto switch to the HSP/HPF profile didn't work and after a manual switch the headset would drop out during a conversation. I reverted to pulseaudio and invested a bit more time, now I am _almost_ there : I had to add the following to ~/.config/pulse/default.pa .include /etc/pulse/default.pa .nofail unload-module module-bluetooth-policy .fail .ifexists module-bluetooth-policy.so load-module module-bluetooth-policy auto_switch=2 .endif .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif to get the autoswitch to work. I am happy to report that in slack (from snap) the audio now behaves just right and friends tell me I no longer sound like a robot. Unfortunately this still doesn't work with zoom and there seems to be multiple issues. They probably come from zoom itself but I am unsure what to report to them. according to https://gavv.github.io/articles/pulseaudio-under-the- hood/#autodetecting-properties it should be possible to make pulseaudio understand that it has to switch profiles by changing /usr/share/applications/Zoom.desktop and adding Telephony to the categories. I have not been able to make this work without auto_switch=2 Here are two scenarios that fail: after a fresh boot (so all the stars are aligned), start zoom, create a new meeting, start the recording, say a few words, stop the recording, stop the meeting, open the resulting audio or video file the sound is bad when it is expected to be good. After a fresh boot (so all the stars are aligned), start zoom, go to settings-> audio, after doing this my headset is non functional and I must shut it down and start it back up to restore functionality. can someone help me determine what zoom is doing wrong ? I will also try a few other apps in the coming weeks -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@yrogge re: How is it possible: I am not familiar with Ubuntu process, but it is common practice that security updates have high priority, and if there is something urgent enough, the release process should have a way to make a "hotfix" release directly from the previous one, before the (ongoing) review process of the "next master" is done. (the changelog does not seem too urgent, but who knows - no idea what those issues were... https://launchpad.net/ubuntu/+source/linux/5.13.0-25.26) Probably the current "master-next" branch (which includes this fix) will have to be rebased/merged on top of the new master (-25) and maybe get a new tag "...-26" or something. However, I am a little concerned that I cannot find the -24.24 kernel in the proposed repo. Robot message above said it needs to be confirmed in 5 days, but people need to be able to DL it to confirm. Maybe they will re-add it after it gets a new tag as -26 ? We may need some input from ubuntu devs... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Hi Louis, Thank you very much for reporting the issue and helping us debug and verify the fix! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Invalid Bug description: [Impact] The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 Author: Lenny Szubowicz Date: Fri Sep 4 21:31:05 2020 -0400 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. [Test case] The kernel need to boot properly with SEV enabled. [Potential regression] The fix is very specific and restricted and should cause regressions, however it touches ioremap that is widely used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1956762] Re: linux-azure: Set CONFIG_CMA=n for arm64
Marking Invalid as this setting requires more research. ** Changed in: linux-azure (Ubuntu Hirsute) Status: In Progress => Invalid ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1956762 Title: linux-azure: Set CONFIG_CMA=n for arm64 Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Hirsute: Invalid Bug description: SRU Justification [Impact] CONFIG_CMA was inadvertently enabled during arm64 development. It should be set the same as amd64. [Test Case] Check the config file from buildinfo for CONFIG_CMA=n [Where things could go wrong] Attempts to allocate large chunks of contiguous RAM could fail. [Other Info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1956762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I can confirm that either -24 and -25 do not work on my ThinkPad E15 Gen 2 (The ThinkPad T580 of my company has never had an issue with this). Every time I see a kernel upgrade in my work ThinkPad, I go excited to my personal ThinkPad just to find out it didn't solve the problem :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
Note above patches causes regression with SEV feature, which has been subsequently fixed. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-azure-5.8 source package in Focal: Fix Released Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot
** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956984 Title: hirsute:linux 5.11.0-45.49 fails to boot Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: [ Impact ] hirsute:linux 5.11.0-45.49 is not booting on several systems/instances. The boot failure is caused at least in most of the cases by systemd services failing to start. On a amd64 test VM the journald service times out when it's configured to use any storage type (which is the default config). [ Fix ] I was able to boot a VM with the following commit reverted: 327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP has hwpoisoned subpage for PMD page fault [ Additional Info ] On an affected VM, after a bit more than 1 hour after booting I get the following soft lockup which helped identify a suspicious commit: [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [systemd-journal:478] [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover i2c_piix4 pata_acpi floppy [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 5.11.0-45-generic #49-Ubuntu [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [12164.211653] RIP: 0010:xas_load+0x33/0x80 [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83 [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246 [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: b17440c7fb78 [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 92d28674b750 [12164.211666] R10: R11: R12: 003b [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 61c8864680b583eb [12164.211669] FS: 7fdf28760900() GS:92d2fdc8() knlGS: [12164.211670] CS: 0010 DS: ES: CR0: 80050033 [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 06e0 [12164.211675] Call Trace: [12164.211678] find_get_entry+0x5a/0x160 [12164.211682] find_lock_entry+0x2d/0x120 [12164.211685] shmem_getpage_gfp+0xe8/0x8c0 [12164.211687] ? asm_sysvec_apic_timer_interrupt+0x12/0x20 [12164.211691] shmem_fault+0x7b/0x220 [12164.211693] ? file_update_time+0x62/0x140 [12164.211696] __do_fault+0x3c/0xe0 [12164.211699] do_shared_fault+0x19/0xb0 [12164.211701] do_fault+0x1cd/0x1f0 [12164.211704] handle_pte_fault+0x1e5/0x260 [12164.211706] __handle_mm_fault+0x59a/0x7c0 [12164.211709] ? timerqueue_add+0x68/0xa0 [12164.211711] handle_mm_fault+0xd7/0x2b0 [12164.211714] do_user_addr_fault+0x1a0/0x450 [12164.211717] exc_page_fault+0x69/0x150 [12164.211720] ? asm_exc_page_fault+0x8/0x30 [12164.211722] asm_exc_page_fault+0x1e/0x30 [12164.211723] RIP: 0033:0x7fdf28fbece1 [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287 [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 7fdf28521fd8 [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 7fdf28522018 [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 0003afd8 [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 002b [12164.211734] R13: 23e0650ff2b8eb94 R14: R15: 7fffd18c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1
https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4754/+packages build in progress. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to downgrade gcc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957072] [NEW] linux-azure-fde fails to install on top of an older version
Public bug reported: Currently linux-azure-fde does not replace the grub binary when a previous version of the same kernel is already installed. That was included on purpose to avoid breaking VMs while re-sealing is not ready and it will eventually be removed. However the meta package linux-image-azure-fde fails to install on top of an older version because its preinst script tries to symlink a link that already exists. ** Affects: linux-meta-azure-fde (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: Fix Committed ** Changed in: linux-meta-azure-fde (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-meta-azure-fde (Ubuntu) Status: New => In Progress ** Changed in: linux-meta-azure-fde (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure-fde in Ubuntu. https://bugs.launchpad.net/bugs/1957072 Title: linux-azure-fde fails to install on top of an older version Status in linux-meta-azure-fde package in Ubuntu: Fix Committed Bug description: Currently linux-azure-fde does not replace the grub binary when a previous version of the same kernel is already installed. That was included on purpose to avoid breaking VMs while re-sealing is not ready and it will eventually be removed. However the meta package linux-image-azure-fde fails to install on top of an older version because its preinst script tries to symlink a link that already exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure-fde/+bug/1957072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1
We are suspecting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 and trying to do builds with it reverted. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 Status in gcc-11 package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to downgrade gcc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944426] Re: Delay sending data after wireless roaming between APs
The patch proposed and accepted here is a partial fix for this bug. https://marc.info/?l=linux-netdev=163579523718765 It adds an option for the wifi supplicant to choose not to clear the ARP cache when roaming. https://github.com/torvalds/linux/commit/fcdb44d08a95003c3d040aecdee286156ec6f34e https://github.com/torvalds/linux/commit/18ac597af25e9760b76471524096f5b29eb820e6 https://github.com/torvalds/linux/commit/f86ca07eb5310a1bdc7032458c7f76862f5a1552 The iwd supplicant adds a patch here to use this which is the other half of the fix: commit 873924a027ad2166436b8117a6bb84ce980ad7f3 Author: James Prestwood Date: Wed Nov 3 15:15:01 2021 -0700 station: set evict_nocarrier sysfs option during roaming If the kernel supports evict_nocarrier set this during the roam to prevent packet delays post roam. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1944426 Title: Delay sending data after wireless roaming between APs Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: ## Summary Any time I roam from one access point to another (same SSID) I start receiving packets instantly after the roam is successful but experience a delay of roughly 1 second before I can send packets out. I have seen this with multiple configurations listed below. I started seeing this delay after upgrading from Ubuntu 16.04 to 18.04 and using the debians from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I can see the bug was introduced between v4.19 and v4.20-rc1. ## Configurations I have tested multiple laptops and machines with different software to narrow down where the bug might be. All of these configurations showed the bug. - Distro(kernel) version - 20.04 (5.4, 5.8, 5.11, 5.14-rc7), Kali 2021.2 (5.10) - Hardware(driver): intel (iwlwifi), qualcomm (ath10k), realtek. - Supplicant: iwd and wpa_supplicant - Manager: iwd, systemd-networkd, NetworkManager - Data: ping, iperf3 (tcp and udp), custom python udp script - APs: Meraki MR46, tp-link decos ## Reproduction The bug is relatively easy to reproduce if you have multiple APs on the same SSID available. The simplest way is to start up a `ping -i 0.2 ` and then walk between the APs until it roams. It is also possible to use `wpa_cli roam `. For more accurate testing I was using a simple python script that spams udp packets and then using `tcpdump` to record the packets for viewing in wireshark. ## Example output Here is the output of the simplest test that still shows the issue (ping + tcpdump + iwd + 5.11.0-27-generic): [https://pastebin.com/92TKKktb](https://pastebin.com/92TKKktb) My naive tl;dr of that data is: - 30.322638 - we start to roam which falls between icmp_seq=121 and icmp_seq=122. - 30.415411 - roam is complete - 30.424277 - iwd is sending and receiving neighbor reports over the link - 31.358491 - an ARP request is sent out (why is the ARP cache cleared?) - 31.367930 - ARP response - packets start being sent again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 10:12:40 2021 InstallationDate: Installed on 2019-08-09 (773 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1944426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
This bug was fixed in the package linux - 5.4.0-94.106 --- linux (5.4.0-94.106) focal; urgency=medium * focal/linux: 5.4.0-94.106 -proposed tracker (LP: #1956628) * [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled (LP: #1956575) - x86/ioremap: Map EFI-reserved memory as encrypted for SEV -- Khalid Elmously Thu, 06 Jan 2022 16:56:46 -0500 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Invalid Bug description: [Impact] The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 Author: Lenny Szubowicz Date: Fri Sep 4 21:31:05 2020 -0400 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Hello everyone, We have released a impish:linux kernel yesterday containing a fix for a critical security issue and a fix for this bug. The version is 5.13.0-25.26, which has the fixes applied on top of 5.13.0-23. Could you please update to 5.13.0-25 and check whether this kernel really fixes the amdgpu issue? Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-23-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry Fix: upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is disabled in Picasso.") Patch was included in the Impish kernel in -proposed (5.13.0.24.24) from an upstream patch set. multiple confirmations the problem is resolved with the kernel in -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown
I have the same problem with a computer : HP 17-ca0026nf AMD A6-9225 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Same on my side. Kernel Version -25 does not boot on ThinkPad E14 Gen3 and is stuck on Lenovo screen. Version -24 works as aspected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
** Changed in: linux-aws (Ubuntu Jammy) Assignee: Tim Gardner (timg-tpi) => Sagi (sagigrim) ** Changed in: linux-aws (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Focal: Confirmed Status in linux-aws source package in Hirsute: Confirmed Status in linux-aws source package in Impish: Confirmed Status in linux-aws source package in Jammy: Fix Released Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957058] Re: snd_hda_intel 0000:00:1f.3: azx_get_response timeout
** Attachment added: "apport.alsa-base.3ri5rd50.apport" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1957058/+attachment/5553322/+files/apport.alsa-base.3ri5rd50.apport ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Confirmed ** Description changed: - Install focal Dell XPS 9370 has no audio function, there is no soundcard - under /proc/asound and got below kernel error: + Install focal on Dell XPS 9370 has no audio function, there is no + soundcard under /proc/asound and got below kernel error: kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: hdaudio hdaudioC0D0: no AFG or MFG node found kernel: snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x200f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1957058 Title: snd_hda_intel :00:1f.3: azx_get_response timeout Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: Install focal on Dell XPS 9370 has no audio function, there is no soundcard under /proc/asound and got below kernel error: kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: hdaudio hdaudioC0D0: no AFG or MFG node found kernel: snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x200f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1957058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
I can see this fix on Jammy tree as well. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934293 Title: Add l2tp.sh in net from ubuntu_kernel_selftests back Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures caused by this test in the test report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957058] [NEW] snd_hda_intel 0000:00:1f.3: azx_get_response timeout
Public bug reported: Install focal Dell XPS 9370 has no audio function, there is no soundcard under /proc/asound and got below kernel error: kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: hdaudio hdaudioC0D0: no AFG or MFG node found kernel: snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x200f ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1957058 Title: snd_hda_intel :00:1f.3: azx_get_response timeout Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Install focal Dell XPS 9370 has no audio function, there is no soundcard under /proc/asound and got below kernel error: kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: snd_hda_intel :00:1f.3: spurious response 0x0:0x0, last cmd=0xfff0005 kernel: hdaudio hdaudioC0D0: no AFG or MFG node found kernel: snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x200f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1957058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Sadly, indeed, the new "security" -25 version seems to be a regression from the "proposed" one. How is it possible? I confirm that the -25 version doesn't boot on a Lenovo ThinkPad E15 G2. And classically, the proposed version disappears when it is superseded by another one. Hopefully, I had marked it in a "hold" status. I thought that the patch was OK and definitely integrated. What happened? Who decided to suppress it? There is an obvious problem with the version management in the Ubuntu Linux kernel. Please consider to correct all this poor bad process! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some thinkpads we may get a kernel panic at boot, because the elantech driver (trakcpad) can trigger out-of-bounds access in the stack. [Test case] Simply boot the kernel on one of the affected systems (e.g., Thinkpad E14 Gen2). [Fix] Prevent the stack out of bound access by applying the following upstream commit (from linux-next): 1d72d9f960cc ("Input: elantech - fix stack out of bound access in elantech_change_report_id()") [Regression potential] The fix is touching the elantech driver, so we could only see regressions with this specific trackpad/mouse driver. [Original bug report] I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910840] Re: [nvidia] Xorg freeze
*** This bug is a duplicate of bug 1955297 *** https://bugs.launchpad.net/bugs/1955297 Moved to bug 1955297. ** This bug has been marked a duplicate of bug 1955297 Xorg freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910840 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After login the screen freezes with mouse pointer duplicating. No operations can be performed .Need to do hard reboot.This started happening after upgrade(5.0.58) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:46:45 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-58-generic, x86_64: installed nvidia, 390.138, 5.4.0-59-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2020-11-02 (68 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903288] Comment bridged from LTC Bugzilla
(builds are ongoing ...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #2 - Daniel John Axtens - 2020-11-05 20:15:10 == This is the kernel side of changes needed for LPAR/guest secure boot. Because Ubuntu keeps its kernels so wonderfully up to date, I don't think there are any extra patches you need to pick up. (I'll double- check against the 21.04 tree once my git pulls finish!) However, we potentially need some configuration changes to make sure kexec-ing into a crashdump kernel still works. Because Lockdown requires that kexec kernels are signed by a key trusted by IMA, the public key for used for signing the kdump kernel needs to be in the IMA keyring or the platform keyring. For host secure boot (and in the UEFI case), it's loaded into the platform keyring. But in the case of guest secure boot with static keys, it's not loaded into the platform keyring so it needs to be loaded into the IMA keyring. This is easy enough to do. Firstly, load the Secure Boot CA into the .primary_trusted_keys keyring via the CONFIG_SYSTEM_TRUSTED_KEYS property. We assume the key used to sign the kernel is signed by this CA. Then, enable IMA_LOAD_X509, which allows certificates signed by a key on the .primary_trusted_keys keyring to be loaded into the IMA keyring. Then set IMA_X509_PATH to provide a path to the signing key on installed file system. (It may also be possible to do this step in userspace, so long as the CA is trusted by the kernel.) Then that key will be loaded into the .ima keyring at boot and be used to appraise the kexec kernel for crashdumps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955297] Re: Mouse freezes
Thanks for the bug reports. Next time the freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955297 Title: Mouse freezes Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Mouse freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 18 15:24:35 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (132 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (117 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp