[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Alright, I checked with Chris Chiu, he confirms that all the tests kernels that he provided don't have -fcf-protection=none. However, we still don't think that touching this compiler option is a proper fix for the bug, more likely it's just hiding the problem, so we could still have a potential stack corruption somewhere. If possible I would like to test a kernel with KASAN enabled to see if we can get additional information about the stack corruption. I've prepared another test kernel (latest 5.13.0-22-generic w/ KASAN enabled): https://kernel.ubuntu.com/~arighi/lp1945590/ If anybody could test this and share the kernel oops/panic info here it'd be great! And hopefully this will help us to understand exactly where and how the stack corruption happens. -- You 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: Confirmed Bug description: 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 1929903] Re: [EHL][TGL][ADL][ICX] Enable Time Coordinated Compute interface driver
** Summary changed: - [EHL][TGL][ADL][ICX-D] Enable Time Coordinated Compute interface driver + [EHL][TGL][ADL][ICX] Enable Time Coordinated Compute interface driver ** Description changed: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology - Hardware: Tiger Lake & Elkhart Lake & Alder Lake & ICX-D + Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure-intel- tcc-tools-in-bios.html -- 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/1929903 Title: [EHL][TGL][ADL][ICX] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux-intel package in Ubuntu: Fix Released Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: Fix Released Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929903] Re: [EHL][TGL][ADL][ICX-D] Enable Time Coordinated Compute interface driver
** Summary changed: - [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver + [EHL][TGL][ADL][ICX-D] Enable Time Coordinated Compute interface driver ** Description changed: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology - Hardware: Tiger Lake & Elkhart Lake & Alder Lake + Hardware: Tiger Lake & Elkhart Lake & Alder Lake & ICX-D Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure-intel- tcc-tools-in-bios.html ** Tags added: iotg-ixc ** Tags removed: iotg-ixc ** Tags added: iotg-icx -- 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/1929903 Title: [EHL][TGL][ADL][ICX] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux-intel package in Ubuntu: Fix Released Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: Fix Released Status in linux-intel-5.13 source package in Focal: Fix Released Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake & Ice Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
@kaihengfeng I just switched to linux-oem-20.04d (5.14.0.1007.7) and, wow, it works like a charm. The Wi-Fi 6 throughput is impressive. Thanks a bunch! Régis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950410] Re: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable
** Changed in: blueman (Ubuntu) Status: New => Incomplete ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-mate Status: New => Incomplete -- 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/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: Incomplete Status in blueman package in Ubuntu: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as
[Kernel-packages] [Bug 1946200] Re: With the Nvidia driver installed there is no option to use Wayland on the login screen
** Summary changed: - With Nvidia-470 there is no option to use Wayland on the login screen + With the Nvidia driver installed there is no option to use Wayland on the login screen ** Tags added: jammy ** Also affects: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-495 (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With the Nvidia driver installed there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950410] Re: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable
Run apport-collect 1950410 ** Tags removed: hirsute ** Tags added: impish ** Also affects: blueman (Ubuntu) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- 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/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: New Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: New Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as
[Kernel-packages] [Bug 1941963] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock
[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/1941963 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock Status in linux package in Ubuntu: Expired Bug description: Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520 From /proc/version: Linux version 5.11.0-27-lowlatency (buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 17:06:56 UTC 2021 # apt-cache policy shim-signed shim-signed: Installed: 1.40.7+15.4-0ubuntu9 Candidate: 1.40.7+15.4-0ubuntu9 Version table: *** 1.40.7+15.4-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages >What you expected to happen Running `apt upgrade` would complete without issue. >What happened instead System hard lock, becomes completely unresponsive both from the local terminal and over established SSH. Eventually memory is exhausted and the machine reboots. Upon restart, running `apt upgrade` returns the error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Running `dpkg --configure -a` attempts to complete installation of shim-signed, segfaults, requiring a cold boot. Only a fraction of the errors generated get written to the logs before the crash as the crash prevents a final flush to disk. From a remote machine I tailed several logs and triggered the crash again, then copied the results from the terminal and attached to report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943154] Re: [i915] My resolution has changed to 800x600, it was 1600x900 before
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Expired -- 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/1943154 Title: [i915] My resolution has changed to 800x600, it was 1600x900 before Status in linux-hwe-5.11 package in Ubuntu: Expired Bug description: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 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-hwe-5.11/+bug/1943154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943239] Re: [amdgpu] /dev/dri/card0 is missing
[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/1943239 Title: [amdgpu] /dev/dri/card0 is missing Status in linux package in Ubuntu: Expired Bug description: the second monitor is not connected on laptop MSI Modern 14 B4MW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 11:52:09 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12c8] InstallationDate: Installed on 2021-09-09 (1 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) MachineType: Micro-Star International Co., Ltd. Modern 14 B4MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=54f1902f-8670-4bf3-9b25-b3ae9ba6e80c ro net.ifnames=0 biosdevname=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14DKAMS.114 dmi.board.asset.tag: Default string dmi.board.name: MS-14DK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14DKAMS.114:bd06/02/2021:svnMicro-StarInternationalCo.,Ltd.:pnModern14B4MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14DK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B4MW dmi.product.sku: 14DK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950355] Re: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon
After validating that I didn't seem to get issues with 20.04.2 I fully replaced 20.04.3 with the previous version. I can edit the grub config, but would that impact a live disk? If yes, I can try editing grub, loading into the .2 version on a live disk, and play around until I see an issue. Also worth pointing out that I will sometimes see no graphics issues for a while, and other times see graphics issues constantly (which is also in line with the screen connection hypothesis). It's possible the same is true for 20.04.3 -- I may just not have seen the graphical irregularities appear yet. Let me know about the grub config. -- 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/1950355 Title: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: (Initial post on ask ubuntu, copy pasted: https://askubuntu.com/questions/1359955/intense-screen-flickering- vertical-rainbow-bars-display-problems-on-ubuntu-20) Starting today (Aug 24) I observed intense screen flickering and tearing on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I know, there were no shutdowns, updates, or changes. I observed this behavior once the machine started up from sleep. Throughout the day I have restarted (and powered down) the machine several times, but the problem persists. Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7 Here is an image: https://i.stack.imgur.com/RgLvB.jpg This video was taken from a clean Ubuntu install USB, so I don't think it has to do with anything I've installed or updated in the past. The system does not have any other operating systems on it (its not dual booted). I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @ 1.90GHz × 8 processor, so I don't think the issue is available processing power (although the integrated graphics could be bad). I'm already using Wayland. I tried everything in the following links: Ubuntu screen flickering https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/ The flickering is most noticeable in Chrome/Firefox (regardless of enabling/disabling hardware acceleration or setting any chrome://flags). However, I've also observed it with just editing Vim in terminal. EDIT: A month later, still experiencing this issue. This problem really seems to come and go -- it will go days without issue, and then have days again where it is constant. I've noticed it on all browsers. I've noticed that closing the webbrowser seems to resolve the issue most of the time. I've noticed that this is not an issue on any extended screens, just the main screen. --- Since the above post, I tried booting into a clean live disk running Ubuntu 20.04.2. This actually worked fine, and I did not observe any strange graphical effects. As per the reply on ask ubuntu, I decided to file this bug. --- Ubuntu release Description: Ubuntu 20.04.3 LTS Release: 20.04 xorg package version: xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-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: Tue Nov 9 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2021-03-15 (239 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20QDS3B800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2020
[Kernel-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)
** Changed in: linux Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912052]
The above change is in upstream: https://lore.kernel.org/alsa- devel/20211104155726.2090997-1-pe...@perex.cz/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
*** This bug is a duplicate of bug 1813733 *** https://bugs.launchpad.net/bugs/1813733 Chiming in that I also experience this issue on my Razer Blade 17 (2021) running ElementaryOS 6 (5.11.0-38-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/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950355] Re: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon
At first this looks like a hardware fault to me. It looks like what happens when I replace a laptop screen and it doesn't get a clean electrical connection. The same can happen if it has received some bumps and intermittently loses connections on some pins. However there's a chance this is a kernel bug and your observation that 20.04.2 does not have a problem supports that theory... Please: 1. Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0" 2. Run: sudo update-grub 3. Reboot. Does that fix the problem? ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Incomplete -- 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/1950355 Title: Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: (Initial post on ask ubuntu, copy pasted: https://askubuntu.com/questions/1359955/intense-screen-flickering- vertical-rainbow-bars-display-problems-on-ubuntu-20) Starting today (Aug 24) I observed intense screen flickering and tearing on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I know, there were no shutdowns, updates, or changes. I observed this behavior once the machine started up from sleep. Throughout the day I have restarted (and powered down) the machine several times, but the problem persists. Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7 Here is an image: https://i.stack.imgur.com/RgLvB.jpg This video was taken from a clean Ubuntu install USB, so I don't think it has to do with anything I've installed or updated in the past. The system does not have any other operating systems on it (its not dual booted). I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @ 1.90GHz × 8 processor, so I don't think the issue is available processing power (although the integrated graphics could be bad). I'm already using Wayland. I tried everything in the following links: Ubuntu screen flickering https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/ The flickering is most noticeable in Chrome/Firefox (regardless of enabling/disabling hardware acceleration or setting any chrome://flags). However, I've also observed it with just editing Vim in terminal. EDIT: A month later, still experiencing this issue. This problem really seems to come and go -- it will go days without issue, and then have days again where it is constant. I've noticed it on all browsers. I've noticed that closing the webbrowser seems to resolve the issue most of the time. I've noticed that this is not an issue on any extended screens, just the main screen. --- Since the above post, I tried booting into a clean live disk running Ubuntu 20.04.2. This actually worked fine, and I did not observe any strange graphical effects. As per the reply on ask ubuntu, I decided to file this bug. --- Ubuntu release Description: Ubuntu 20.04.3 LTS Release: 20.04 xorg package version: xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-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: Tue Nov 9 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2021-03-15 (239 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20QDS3B800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7
[Kernel-packages] [Bug 1950355] [NEW] Intense screen flickering, vertical rainbow bars, display problems on Ubuntu 20.04, Lenovo X1 Carbon
You have been subscribed to a public bug: (Initial post on ask ubuntu, copy pasted: https://askubuntu.com/questions/1359955/intense-screen-flickering- vertical-rainbow-bars-display-problems-on-ubuntu-20) Starting today (Aug 24) I observed intense screen flickering and tearing on my Ubuntu 20.04.3 on the Lenovo X1 Carbon. As far as I know, there were no shutdowns, updates, or changes. I observed this behavior once the machine started up from sleep. Throughout the day I have restarted (and powered down) the machine several times, but the problem persists. Here is a video example: https://photos.app.goo.gl/516nAe7AUUYnAHzd7 Here is an image: https://i.stack.imgur.com/RgLvB.jpg This video was taken from a clean Ubuntu install USB, so I don't think it has to do with anything I've installed or updated in the past. The system does not have any other operating systems on it (its not dual booted). I'm using basic integrated graphics (Mesa Intel® UHD Graphics 620 (WHL GT2)). System has 16gb of RAM and a Intel® Core™ i7-8665U CPU @ 1.90GHz × 8 processor, so I don't think the issue is available processing power (although the integrated graphics could be bad). I'm already using Wayland. I tried everything in the following links: Ubuntu screen flickering https://www.reddit.com/r/Ubuntu/comments/g78o4e/screen_tearing_in_ubuntu_2004/ The flickering is most noticeable in Chrome/Firefox (regardless of enabling/disabling hardware acceleration or setting any chrome://flags). However, I've also observed it with just editing Vim in terminal. EDIT: A month later, still experiencing this issue. This problem really seems to come and go -- it will go days without issue, and then have days again where it is constant. I've noticed it on all browsers. I've noticed that closing the webbrowser seems to resolve the issue most of the time. I've noticed that this is not an issue on any extended screens, just the main screen. --- Since the above post, I tried booting into a clean live disk running Ubuntu 20.04.2. This actually worked fine, and I did not observe any strange graphical effects. As per the reply on ask ubuntu, I decided to file this bug. --- Ubuntu release Description:Ubuntu 20.04.3 LTS Release:20.04 xorg package version: xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-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: Tue Nov 9 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2021-03-15 (239 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20QDS3B800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=9213d3af-1e40-4621-9964-1212d1070372 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2020 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET55W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDS3B800 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:bvrN2HET55W(1.38):bd08/24/2020:br1.38:efr1.20:svnLENOVO:pn20QDS3B800:pvrThinkPadX1Carbon7th:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:rvnLENOVO:rn20QDS3B800:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDS3B800 dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
Semih, that's not this bug, it's a completely different bug in a different driver. You should open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 2 19:26:01 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-20-generic, x86_64: installed v4l2loopback, 0.12.5, 5.15.0-051500-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:81ee] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ee] InstallationDate: Installed on 2021-10-29 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-051500-generic root=UUID=51509311-ce8a-48fb-9ece-8e018d63fe03 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2020 dmi.bios.release: 15.49 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EE dmi.board.vendor: HP dmi.board.version: 62.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 62.29 dmi.modalias: dmi:bvnInsyde:bvrF.49:bd06/26/2020:br15.49:efr62.29:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:skuX9Z24EA#AB8: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: X9Z24EA#AB8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950385 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: breezy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: Incomplete Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] Re: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950385 Title: HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel Status in linux package in Ubuntu: New Bug description: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950385] [NEW] HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel
You have been subscribed to a public bug: Focal Fossa 20.04.1 HP lt4120 Snapdragon X5 LTE USB modem stopped working from kernel 5.10.x. It is not seen by Network Manager. Everything worked with 5.8.x kernel. I can't use newer kernel if I want work over HP lt4120 Snapdragon X5 LTE modem. I can't test kernel 5.14 & 5.15 in 20.04 due to libc version not compatible with updated libc from Ubuntu 20.04. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- HP lt4120 Snapdragon X5 LTE USB modem not working since 5.10 kernel https://bugs.launchpad.net/bugs/1950385 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950381] Re: Adding landlock to CONFIG_LSM in 5.13 kernels
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950381 Title: Adding landlock to CONFIG_LSM in 5.13 kernels Status in linux package in Ubuntu: Confirmed Bug description: Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it should be added to CONFIG_LSM[3] so that the feature is usable without having to override the lsm parameter on the kernel command line (and reboot). Upstream seems to have it enabled since it was merged before 5.13-rc1.[4] I tried to use landlock this morning on ubuntu 20.04 with kernel linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 and was a bit surprised that it didn't work right away, it returned ENOTSUPP. I had to dig around a bit to see that it needs to be added to CONFIG_LSM before it can actually be used. To make it work, I added the following to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub: lsm=landlock,lockdown,yama,integrity,apparmor Then grub-update + reboot. It'd be great if it was available without having to jump through hoops (and a reboot), but otherwise maybe the above info will help others trying to figure out why landlock isn't working even-though the feature is configured in the kernel. [1] https://www.kernel.org/doc/html/latest/userspace-api/landlock.html [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n9230 [3] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n5722 [4] https://github.com/torvalds/linux/commit/385975dca53eb41031d0cbd1de318eb1bc5d6bb9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 the kernel linked by randomdave above works perfectly. so there is your working kernel, bisect away. (can also confirm the 5.15 kernel still has the bug, every ubuntu kernel since 5.11 has the bug, apart from the unofficial one linked by randomdave 2 replies above.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Confirmed Bug description: 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 1950389] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539348/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539347/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539346/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539352/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539344/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539350/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539351/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539349/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539354/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539345/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539355/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539342/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539343/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539353/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539341/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539340/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: to 1278 F pulseaudio /dev/snd/controlC0: to 1278 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b InstallationDate: Installed on 2018-10-25 ( days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend 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.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 06/27/2018 dmi.bios.release: 15.69 dmi.bios.vendor: Insyde dmi.bios.version: F.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.56 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.56 dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: J5B28EA#ABE dmi.product.version: 097610405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Re: fn keys stopped working after kernel update (HP Pavilion 15-R008NS)
apport information ** Tags added: apport-collected ** Description changed: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: to 1278 F pulseaudio + /dev/snd/controlC0: to 1278 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=2aa88c03-1e8a-4bda-a77c-3cb32660af5b + InstallationDate: Installed on 2018-10-25 ( days ago) + InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: Hewlett-Packard HP 15 Notebook PC + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=UUID=74203cf3-a748-4899-b6f1-7f54ed94b93f ro initcall_debug no_console_suspend + 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.20 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.11.0-40-generic x86_64 + UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. + UpgradeStatus: Upgraded to focal on 2020-05-25 (533 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: False + dmi.bios.date: 06/27/2018 + dmi.bios.release: 15.69 + dmi.bios.vendor: Insyde + dmi.bios.version: F.45 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: 2211 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 86.56 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 86.56 + dmi.modalias: dmi:bvnInsyde:bvrF.45:bd06/27/2018:br15.69:efr86.56:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:skuJ5B28EA#ABE:rvnHewlett-Packard:rn2211:rvr86.56:cvnHewlett-Packard:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV + dmi.product.name: HP 15 Notebook PC + dmi.product.sku: J5B28EA#ABE + dmi.product.version: 097610405F0620180 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1950389/+attachment/5539339/+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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Confirmed Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic),
[Kernel-packages] [Bug 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
Tests are now passing. ** Changed in: ubuntu-kernel-tests Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz test_zz_cleanup_source_tree (__main__.ApparmorTestsuites) Cleanup downloaded source ... ok == FAIL: test_utils_testsuite (__main__.ApparmorTestsuites) Run utils (make check) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1841, in test_utils_testsuite self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 == FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites) Run utils (make check with python3) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1862, in test_utils_testsuite3 self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 -- Ran 58 tests in 1448.768s FAILED (failures=2) 23:36:54 INFO | END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 14 23:36:54 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950389 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: Incomplete Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Does this fix also work for Impish Indri (21.10) because I noticed the
same issue but I was not able to fix the issue by manually changing the
line within /usr/share/initramfs-tools/scripts/zfs.
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
[Impact]
* Users can’t revert to previous snapshots when enabling the hw enablement
stack kernel on focal or using any more recent version.
* The option is available on grub and will let you with a broken system,
partially cloned.
[Test Case]
* Boot on a system, using ZFS and ZSys.
* In grub, select "History" entry
* Select one of the "Revert" option: the system should boot after being
reverted with an older version.
[Where problems could occur]
* The code is in the initramfs, where the generated id suffix for all our
ZFS datasets was empty due to new coreutils/kernels.
* We replace dd with another way (more robust and simple) for generating
this ID.
-
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Re: fn keys stopped working after kernel update (HP Pavilion 15-R008NS)
** Attachment added: "The result of executing `dmidecode -t system`" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+attachment/5539317/+files/dmidecode.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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: New Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Re: fn keys stopped working after kernel update (HP Pavilion 15-R008NS)
** Attachment added: "The result of executing `dmesg`" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+attachment/5539316/+files/dmesg.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/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: New Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] Re: fn keys stopped working after kernel update (HP Pavilion 15-R008NS)
$ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy linux-image-generic-hwe-20.04 linux-image-generic-hwe-20.04: Instalados: 5.11.0.40.44~20.04.18 Candidato: 5.11.0.40.44~20.04.18 Tabla de versión: *** 5.11.0.40.44~20.04.18 500 500 http://mirror.lstn.net/ubuntu focal-updates/main amd64 Packages 500 http://mirror.lstn.net/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://mirror.lstn.net/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: New Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950389] [NEW] fn keys stopped working after kernel update (HP Pavilion 15-R008NS)
Public bug reported: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950389 Title: fn keys stopped working after kernel update (HP Pavilion 15-R008NS) Status in linux package in Ubuntu: New Bug description: In a HP Pavilion 15-R008NS: fn keys stopped working after kernel update. For example, if you press Fn+F3 it's the same as pressing F3. That was the update (from the /var/log/apt/history.log file): Start-Date: 2021-11-09 19:14:19 Commandline: apt full-upgrade Install: linux-image-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-modules-extra-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-modules-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic), linux-headers-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-headers-5.4.0-90:amd64 (5.4.0-90.101, automatic), linux-modules-5.4.0-90-generic:amd64 (5.4.0-90.101, automatic), linux-hwe-5.11-headers-5.11.0-40:amd64 (5.11.0-40.44~20.04.2, automatic), linux-image-5.11.0-40-generic:amd64 (5.11.0-40.44~20.04.2, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-headers-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-libc-dev:amd64 (5.4.0-89.100, 5.4.0-90.101), linux-image-generic:amd64 (5.4.0.89.93, 5.4.0.90.94), linux-image-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic-hwe-20.04:amd64 (5.11.0.38.42~20.04.17, 5.11.0.40.44~20.04.18), linux-generic:amd64 (5.4.0.89.93, 5.4.0.90.94) End-Date: 2021-11-09 19:21:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950388] [NEW] Impish update: upstream stable patchset 2021-11-09
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-09 Ported from the following upstream stable releases: v5.10.71, v5.14.10 from git://git.kernel.org/ tty: Fix out-of-bound vmalloc access in imageblit cpufreq: schedutil: Use kobject release() method to free sugov_tunables scsi: qla2xxx: Changes to support kdump kernel for NVMe BFS cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory ACPI: NFIT: Use fallback node id when numa info in NFIT table is incorrect fs-verity: fix signed integer overflow with i_size near S64_MAX hwmon: (tmp421) handle I2C errors hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field gpio: pca953x: do not ignore i2c errors scsi: ufs: Fix illegal offset in UPIU event trace mac80211: fix use-after-free in CCMP/GCMP RX x86/kvmclock: Move this_cpu_pvti into kvmclock.h KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect() KVM: x86: nSVM: don't copy virt_ext from vmcb12 KVM: nVMX: Filter out all unsupported controls when eVMCS was activated media: ir_toy: prevent device from hanging during transmit RDMA/cma: Do not change route.addr.src_addr.ss_family drm/amd/display: Pass PCI deviceid into DC drm/amdgpu: correct initial cp_hqd_quantum for gfx9 ipvs: check that ip_vs_conn_tab_bits is between 8 and 20 bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog IB/cma: Do not send IGMP leaves for sendonly Multicast groups RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure bpf, mips: Validate conditional branch offsets hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap mac80211: mesh: fix potentially unaligned access mac80211-hwsim: fix late beacon hrtimer handling sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb mptcp: don't return sockets in foreign netns hwmon: (tmp421) report /PVLD condition as fault hwmon: (tmp421) fix rounding for negative values net: enetc: fix the incorrect clearing of IF_MODE bits net: ipv4: Fix rtnexthop len when RTA_FLOW is present smsc95xx: fix stalled rx after link change drm/i915/request: fix early tracepoints dsa: mv88e6xxx: 6161: Use chip wide MAX MTU dsa: mv88e6xxx: Fix MTU definition dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports e100: fix length calculation in e100_get_regs_len e100: fix buffer overrun in e100_get_regs bpf: Exempt CAP_BPF from checks against bpf_jit_limit selftests, bpf: Fix makefile dependencies on libbpf selftests, bpf: test_lwt_ip_encap: Really disable rp_filter UBUNTU: [Config] updateconfigs for ks8851 modules net: ks8851: fix link error scsi: csiostor: Add module softdep on cxgb4 ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup net: hns3: do not allow call hns3_nic_net_open repeatedly net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE net: hns3: fix show wrong state when add existing uc mac address net: hns3: reconstruct function hns3_self_test net: hns3: fix always enable rx vlan filter problem after selftest net: phy: bcm7xxx: Fixed indirect MMD operations net: sched: flower: protect fl_walk() with rcu af_unix: fix races in sk_peer_pid and sk_peer_cred accesses perf/x86/intel: Update event constraints for ICX hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller nvme: add command id quirk for apple controllers elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings debugfs: debugfs_create_file_size(): use IS_ERR to check for error ipack: ipoctal: fix stack information leak ipack: ipoctal: fix tty registration race ipack: ipoctal: fix tty-registration error handling ipack: ipoctal: fix missing allocation-failure check ipack: ipoctal: fix module reference leak ext4: fix loff_t overflow in ext4_max_bitmap_size() ext4: limit the number of blocks in one ADD_RANGE TLV ext4: fix reserved space counter leakage ext4: add error checking to ext4_ext_replay_set_iblocks() ext4: fix potential infinite loop in ext4_dx_readdir() HID: u2fzero: ignore incomplete packets without data net: udp: annotate data race around udp_sk(sk)->corkflag usb: hso: remove the bailout parameter HID: betop: fix slab-out-of-bounds Write in
[Kernel-packages] [Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
The issue seems to have been resolved for me with 5.13.0-7620, while it was still broken with 5.13.0-7614. I realize these are System76 specific kernels, but maybe the trend is the same for the corresponding 5.13.0-20 and 5.13.0-14. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 Status in linux package in Ubuntu: Confirmed Bug description: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 476.956491] [drm] Failed to add display topology, DTM TA is not initialized. [ 488.792533] unplugged [ 529.801179] plugging HDMI into dock [ 536.721076] [drm] DP Alt mode state on HPD: 1 [ 536.792947] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 536.901958] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.906123] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.910288] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.914611] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.919568] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.923725] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.927888] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.932047] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.936451] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.941486] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.945651] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 536.949808] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 537.010093] [drm:drm_dp_send_dpcd_read [drm_kms_helper]]
[Kernel-packages] [Bug 1941893] Re: Improve performance and idle power consumption
** Changed in: amd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1941893 Title: Improve performance and idle power consumption Status in amd: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] This can improve AMD performance for all Zen or newer CPU which support C3 shares cache. [Fix] Its not necessary to flush the caches in software before entering C3. Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8 [Test] This is requested by AMD. [Where problems could occur] Low risk. This only works on AMD Zen CPUs that supports this features. AMD tested it and provided estimated measurement results. Original descriptions A patch queued for 5.15 to change the C3 entry will improve AMD performance. https://lore.kernel.org/patchwork/patch/1478776/ Empirical measurements show: 40-45% improvement in speedometer score. ~15% improvement in idle power. Can you please include in 5.13-oem and 5.14-oem kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1941893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945361] Re: [Yellow Carp] USB4 interdomain communication problems
** Changed in: amd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945361 Title: [Yellow Carp] USB4 interdomain communication problems Status in amd: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Yellow carp w/ SW CM bi-directional interdomain communication may have some problems that the response packets are lost sometimes within the stipulated time. [Fix] Enable the retry by increasing retry count from 1 to 4. The patch is in linux-next (tag next-20211007) and can be found @ https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3 [Test] This is requested and tested by AMD. [Where problems could occur] Low risk. This only affects small number of AMD systems that would excess the time. Systems without problems won't be affected. = Original Description AMD internal team has found that for Yellow carp w/ SW CM bi- directional interdomain communication may have some problems. It's been aligned upstream to increase number of retries to account for these issues. https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3 Can Canonical team please include this in future 5.14-OEM? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1945361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950381] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1950381 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950381 Title: Adding landlock to CONFIG_LSM in 5.13 kernels Status in linux package in Ubuntu: Incomplete Bug description: Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it should be added to CONFIG_LSM[3] so that the feature is usable without having to override the lsm parameter on the kernel command line (and reboot). Upstream seems to have it enabled since it was merged before 5.13-rc1.[4] I tried to use landlock this morning on ubuntu 20.04 with kernel linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 and was a bit surprised that it didn't work right away, it returned ENOTSUPP. I had to dig around a bit to see that it needs to be added to CONFIG_LSM before it can actually be used. To make it work, I added the following to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub: lsm=landlock,lockdown,yama,integrity,apparmor Then grub-update + reboot. It'd be great if it was available without having to jump through hoops (and a reboot), but otherwise maybe the above info will help others trying to figure out why landlock isn't working even-though the feature is configured in the kernel. [1] https://www.kernel.org/doc/html/latest/userspace-api/landlock.html [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n9230 [3] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n5722 [4] https://github.com/torvalds/linux/commit/385975dca53eb41031d0cbd1de318eb1bc5d6bb9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950381] [NEW] Adding landlock to CONFIG_LSM in 5.13 kernels
Public bug reported: Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it should be added to CONFIG_LSM[3] so that the feature is usable without having to override the lsm parameter on the kernel command line (and reboot). Upstream seems to have it enabled since it was merged before 5.13-rc1.[4] I tried to use landlock this morning on ubuntu 20.04 with kernel linux- image-5.13.0-21-generic 5.13.0-21.21~20.04.1 and was a bit surprised that it didn't work right away, it returned ENOTSUPP. I had to dig around a bit to see that it needs to be added to CONFIG_LSM before it can actually be used. To make it work, I added the following to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub: lsm=landlock,lockdown,yama,integrity,apparmor Then grub-update + reboot. It'd be great if it was available without having to jump through hoops (and a reboot), but otherwise maybe the above info will help others trying to figure out why landlock isn't working even-though the feature is configured in the kernel. [1] https://www.kernel.org/doc/html/latest/userspace-api/landlock.html [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n9230 [3] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n5722 [4] https://github.com/torvalds/linux/commit/385975dca53eb41031d0cbd1de318eb1bc5d6bb9 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950381 Title: Adding landlock to CONFIG_LSM in 5.13 kernels Status in linux package in Ubuntu: New Bug description: Since Landlock[1] is enabled in ubuntu 5.13 kernels[2], I wonder if it should be added to CONFIG_LSM[3] so that the feature is usable without having to override the lsm parameter on the kernel command line (and reboot). Upstream seems to have it enabled since it was merged before 5.13-rc1.[4] I tried to use landlock this morning on ubuntu 20.04 with kernel linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 and was a bit surprised that it didn't work right away, it returned ENOTSUPP. I had to dig around a bit to see that it needs to be added to CONFIG_LSM before it can actually be used. To make it work, I added the following to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub: lsm=landlock,lockdown,yama,integrity,apparmor Then grub-update + reboot. It'd be great if it was available without having to jump through hoops (and a reboot), but otherwise maybe the above info will help others trying to figure out why landlock isn't working even-though the feature is configured in the kernel. [1] https://www.kernel.org/doc/html/latest/userspace-api/landlock.html [2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n9230 [3] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/tree/debian.hwe-5.13/config/config.common.ubuntu?h=hwe-5.13#n5722 [4] https://github.com/torvalds/linux/commit/385975dca53eb41031d0cbd1de318eb1bc5d6bb9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.41.42)
All autopkgtests for the newly accepted linux-meta (5.11.0.41.42) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: sysdig/0.27.1-0.2 (armhf) systemd/247.3-3ubuntu3.6 (armhf) 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/hirsute/update_excuses.html#linux-meta [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 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 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
resolved with latest proposed kernel - 5.13.0.22.33 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 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 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.13.0.22.33)
All autopkgtests for the newly accepted linux-meta (5.13.0.22.33) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8 (ppc64el) diffoscope/180 (armhf) 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/impish/update_excuses.html#linux-meta [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Just upgraded my Lenovo L13 Yoga machine to Ubuntu 21.10. Affected by the same bug, had to revert to kernel 5.11. -- You 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: Confirmed Bug description: 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 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/4.15.0.163.152)
All autopkgtests for the newly accepted linux-meta (4.15.0.163.152) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.52 (armhf) 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/bionic/update_excuses.html#linux-meta [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
I'm not sure it's relevant but I'm already on (K)ubuntu 21.10, kernel 5.13.0.20 and the problem is still there. Unless you are looking specifically for feedback from HWE kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949497] Re: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout)
I'm experiencing the problem on radeon driver too. Only way to run without any error is setting power_dpm_state to "battery" (or setting power_dpm_force_performance_level to "low"). It gives gpu fault error: [ 173.274091] radeon :01:00.0: WB enabled [ 173.274093] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 [ 173.274095] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 [ 173.274096] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 [ 173.274097] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c [ 173.274098] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 [ 173.274642] debugfs: File 'radeon_ring_gfx' in directory '0' already present! [ 173.274647] debugfs: File 'radeon_ring_cp1' in directory '0' already present! [ 173.274649] debugfs: File 'radeon_ring_cp2' in directory '0' already present! [ 173.274650] debugfs: File 'radeon_ring_dma1' in directory '0' already present! [ 173.274653] debugfs: File 'radeon_ring_dma2' in directory '0' already present! [ 173.469429] [drm] ring test on 0 succeeded in 1 usecs [ 173.469435] [drm] ring test on 1 succeeded in 1 usecs [ 173.469439] [drm] ring test on 2 succeeded in 1 usecs [ 173.469448] [drm] ring test on 3 succeeded in 4 usecs [ 173.469454] [drm] ring test on 4 succeeded in 3 usecs [ 173.469488] [drm] ib test on ring 0 succeeded in 0 usecs [ 173.469516] [drm] ib test on ring 1 succeeded in 0 usecs [ 173.469542] [drm] ib test on ring 2 succeeded in 0 usecs [ 173.469556] [drm] ib test on ring 3 succeeded in 0 usecs [ 173.469568] [drm] ib test on ring 4 succeeded in 0 usecs [ 173.690183] radeon :01:00.0: GPU fault detected: 146 0x0aa31014 [ 173.690189] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00100DD5 [ 173.690191] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014 [ 173.690192] VM fault (0x04, vmid 1) at page 1052117, write from CB (16) [ 184.196457] Asynchronous wait on fence radeon:radeon.gfx:28 timed out (hint:submit_notify [i915]) [ 184.196439] Asynchronous wait on fence :00:02.0:gnome-shell[1653]:3b6 timed out (hint:intel_atomic_commit_ready [i915]) [ 184.196921] Asynchronous wait on fence radeon:radeon.gfx:26 timed out (hint:submit_notify [i915]) [ 184.232357] radeon :01:00.0: ring 0 stalled for more than 10244msec [ 184.232376] radeon :01:00.0: GPU lockup (current fence id 0x0025 last fence id 0x0029 on ring 0) [ 184.740610] radeon :01:00.0: ring 0 stalled for more than 10752msec [ 184.740635] radeon :01:00.0: GPU lockup (current fence id 0x0025 last fence id 0x0029 on ring 0) [ 185.252668] radeon :01:00.0: ring 0 stalled for more than 11264msec [ 185.252690] radeon :01:00.0: GPU lockup (current fence id 0x0025 last fence id 0x0029 on ring 0) [ 185.764745] radeon :01:00.0: ring 0 stalled for more than 11776msec [ 185.764771] radeon :01:00.0: GPU lockup (current fence id 0x0025 last fence id 0x0029 on ring 0) ... I tried the 4.19 kernel 1-2 weeks ago (with Ubuntu 20.04 and latest mesa drivers), application launches fine and runs without any error. But after playing games for hours, sometimes it gives the gfx timeout error again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949497 Title: [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) Status in linux package in Ubuntu: Confirmed Bug description: When i try to run anything with my dGPU (Radeon R5 M430), application freezes. But when i set "power_dpm_state" to "battery", or amdgpu.dpm=0 in boot options, it runs fine. i get errors like this: [ 56.647827] [drm] PCIE gen 3 link speeds already enabled [ 56.649064] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 83.707076] [drm] PCIE gen 3 link speeds already enabled [ 83.708350] amdgpu :01:00.0: amdgpu: PCIE GART of 256M enabled (table at 0x00F4). [ 94.813212] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=47, emitted seq=49 [ 94.814219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process glmark2 pid 4471 thread glmark2:cs0 pid 4473 [ 94.815125] amdgpu :01:00.0: amdgpu: GPU recovery disabled. [ 95.069353] Asynchronous wait on fence :00:02.0:gnome-shell[1648]:3c6 timed out (hint:intel_atomic_commit_ready [i915]) [ 95.069353] Asynchronous wait on fence dma_fence_chain:unbound:1 timed out (hint:submit_notify [i915]) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-051500-generic x86_64 ApportVersion: 2.20.11-0ubuntu71
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950339] [NEW] Screen stays black after going idle or waking up from suspend on AMD laptop
Public bug reported: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1950339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
The kernel Chris Chiu compiled here: https://people.canonical.com/~mschiu77/lp1941773/I/ works with my Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7 4700u with radeon graphics × 8 (AMD Renoir graphic). In another thread (https://www.mail-archive.com/ubuntu- b...@lists.ubuntu.com/msg5949850.html) Chris Chiu states "It should be caused by the kbuild flag `-fcf-protection=none` and this will not be applied for the UBUNTU release image." -- You 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: Confirmed Bug description: 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 1945531] Re: kernel panic at boot
Kernel panic still happening in linux-image-5.13.0-21-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/1945531 Title: kernel panic at boot Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: On do-release-upgrade to Impish with the 5.13 kernel the boot messages stop scrolling at: fb0: switching to amdgpudrmfb from EFI VGA The system may be continuing to boot but the screen stops updating. The 5.11 and 5.12 kernels both boot correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950336] [NEW] hirsute/linux-azure: Backport more CIFS patches
Public bug reported: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport. Two patches have been added since the original request (LP: #1947027). [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Hirsute) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: New ** Description changed: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport. Two patches have - been added since the original request. + been added since the original request (LP: #1947027). [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 ** Also affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1950336 Title: hirsute/linux-azure: Backport more CIFS patches Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Hirsute: New Bug description: [SRU Justification] [Impact] Microsoft has asked to backport cifs patches up through v5.15-rc3 from git://git.samba.org/sfrench/cifs-2.6.git 5.11-backport. Two patches have been added since the original request (LP: #1947027). [Test Case] Connect to a SAMBA server [Where things might go wrong] Connections may fail, or have poor performance. [Other Info] SF: #00316229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1950336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 here, no change with Kernel 5.15 (Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7 4700u with radeon graphics × 8 (AMD Renoir graphic)). @Andrea I might not send my hardware, but is there any other information I can give that might help to identify the error? -- You 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: Confirmed Bug description: 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 1949770] Re: Enable arm64 for Hyper-V guests
** Also affects: linux-meta-azure (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-signed-azure (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-signed-azure (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-signed-azure (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-meta-azure (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-meta-azure (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-meta-azure (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-signed-azure (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => New ** Changed in: linux-azure (Ubuntu Jammy) Assignee: Tim Gardner (timg-tpi) => (unassigned) ** Changed in: linux-azure (Ubuntu Jammy) Importance: Medium => Undecided -- 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/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-signed-azure package in Ubuntu: New Status in linux-azure source package in Hirsute: In Progress Status in linux-meta-azure source package in Hirsute: In Progress Status in linux-signed-azure source package in Hirsute: In Progress Status in linux-azure source package in Impish: New Status in linux-meta-azure source package in Impish: New Status in linux-signed-azure source package in Impish: New Status in linux-azure source package in Jammy: New Status in linux-meta-azure source package in Jammy: New Status in linux-signed-azure source package in Jammy: New Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942759] Re: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install
@aseligmann Backporting sounds like too much effort for now indeed. At least it is good to know that I'm not the only one experiencing these issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942759 Title: No touchpad detected on 'HP ZBook Firefly G8 (1G3U1AV)' after fresh install Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS The touchpad is not detected with or without the Logitech M705 mouse plugged in. cat /proc/bus/input/devices Outputs: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=20 0 0 1500f0210 43803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=046d Product=101b Version=0111 N: Name="Logitech M705" P: Phys=usb-:00:14.0-4/input2:1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.2/0003:046D:C52B.0004/0003:046D:101B.0005/input/input14 U: Uniq=101b-fc-92-33-df H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input15 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input16 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input17 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input18 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP HD Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input19 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=04f2 Product=b6bf Version=0013 N: Name="HP HD Camera: HP IR Camera" P: Phys=usb-:00:14.0-2/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.2/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 6 11:37:52 2021 InstallationDate: Installed on 2021-09-06 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 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.4/+bug/1942759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949882] Re: linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Focal) Status: In Progress => 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/1949882 Title: linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: Fix Committed Bug description: SRU Justification [Impact] Communications between the RDMA device and the driver are not complete. The shared structure definition of struct efa_admin_feature_queue_attr_desc is incorrect. [Test Plan] Amazon tested [Where things could go wrong] This patch could further compromise driver/device communications. [Other Info] SF: #00322369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
This bug is awaiting verification that the linux/5.13.0-22.22 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. 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/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
SRU request submitted to the Ubuntu kernel team mailing list for impish, hirsute and focal: https://lists.ubuntu.com/archives/kernel-team/2021-November/thread.html#125581 Changing status to 'In Progress' for impish, hirsute and focal. ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Description changed: + SRU Justification: + == + + [Impact] + + * The kernel is unable to read partitions on virtio-block DASD (on KVM). + That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. + This issue can either occur after a fresh installation or after an upgrade. + + * The virtio specification virtio-v1.1-cs01 states: "Transitional devices + MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not + been acknowledged by the driver." + And this is what QEMU as of 6.1 has done relying solely on + VIRTIO_F_VERSION_1 for detecting that. + + * But the specification also says: "... the driver MAY read (but MUST + NOT write) the device-specific configuration fields to check that it can + support the device ..." before setting FEATURES_OK. + + * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 + for detecting legacy drivers will return data in legacy format. + In particular, this implies that it's in big endian format for + big endian guests. This naturally confuses the driver that expects + little endian in the modern mode. + + * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation + is done. + + * 'verify' is called before virtio_finalize_features(), so a transitional + s390 virtio device still serves native endian (i.e. big endian) config space, + while the driver knows that it is going to accept VERSION_1, + so when reading the config space, it assumes it got little endian, and byteswaps. + + * For QEMU, we can work around the issue by writing out the feature bits with + VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for + this. This isn't enough to address all vhost devices since these do not get + the features until FEATURES_OK, however it looks like the affected devices + actually never handled the endianness for legacy mode correctly, so at least + that's not a regression. + + [Fix] + + * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write + back F_VERSION_1 before validate" + + [Test Case] + + * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. + + * This Ubuntu KVM host can either be installed on FCP or DASD storage, + but at least one DASD disk need to be reserved for a KVM guest. + + * Now hand over the reserved DASD disk (low-level formatted using dasdfmt + and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine + (e.g. using a virsh VM config). + + * Try to install an Ubuntu KVM virtual machine using this DASD disk, + that includes the check and read of the partition table. + + [Where problems could occur] + + * First of all requested commit contains one additional if statement; + and is due tothat relatively traceable. + + * But the change is in /drivers/virtio/virtio.c, means in common code! + + * This issue obviously affects big endian systems only. + + * But if done wrong, it may effect in worst-case little endian systems, + too! + + * But the if statement explicitly checks for + '!virtio_legacy_is_little_endian()'. + + * Only virtio net and virtio blk devices seem to be affected. + + * And the commit/solutions was in-depth discussed upstream here: + https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u + + [Other] + + * Patches are upstream accepted with since 5.15-rc6 + and tagged for upstream stable #v4.11. + Hence jammy is not affected. + + * Request was to add the patches to focal / 20.04, + but to avoid potential regressions on upgrades, + the patches need to be added to impish and hirsute, too. + + * Fortunately cherry-picking the commit works cleanly + from all the affected Ubuntu releases. + + __ + Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a - transitional s390 virtio device still serves native endian - (i.e. big endian) config space, while the driver knows that it -
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] selftests net will fail on i386, requiring engineers time to investigate, or leading to new BPF failures to be ignored. [Fix] The fix is only to tests. [Test case] Run test_bpf.sh from tools/testing/selftests/net/. [Potential regression] Tests could fail on other architectures. This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
This bug is awaiting verification that the linux/5.4.0-91.102 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == This issue was only spotted on i386 Bionic kernel. #146/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! 0: (bf) r6 = r10 1: (07) r6 += -8 2: (15) if r1 == 0x0 goto pc+3 R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 3: (bf) r2 = r10 4: (07) r2 += -76 5: (7b) *(u64 *)(r6 +0) = r2 6: (55) if r1 != 0x0 goto pc+1 R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp 7: (7b) *(u64 *)(r6 +0) = r1 8: (79) r1 = *(u64 *)(r6 +0) 9: (79) r1 = *(u64 *)(r1 +68) #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (71) r0 = *(u8 *)(r1 +68) invalid bpf_context access off=68 size=1 #353/p check bpf_perf_event_data->sample_period half load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (69) r0 = *(u16 *)(r1 +68) invalid bpf_context access off=68 size=2 #354/p check bpf_perf_event_data->sample_period word load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (61) r0 = *(u32 *)(r1 +68) invalid bpf_context access off=68 size=4 #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (79) r0 = *(u64 *)(r1 +68) invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 23 08:23 seq crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
This bug is awaiting verification that the linux/5.4.0-91.102 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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947161] Re: ACL updates on OCFS2 are not revalidated
This bug is awaiting verification that the linux/5.13.0-22.22 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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-impish
** Tags added: verification-needed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947161
Title:
ACL updates on OCFS2 are not revalidated
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947161] Re: ACL updates on OCFS2 are not revalidated
This bug is awaiting verification that the linux/5.4.0-91.102 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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947161
Title:
ACL updates on OCFS2 are not revalidated
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947709] Re: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active"
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947709 Title: Drop "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Confirmed Bug description: [Impact] "UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file while vmscan is active" has been applied to fix a page leaking issue. However a slightly different fix has been applied upstream: 9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page leak in cachefiles_read_backing_file while vmscan is active Basically we are fixing the same issue in two different ways at the same time, but even worse our patch an introduce a potential NULL pointer dereference: we do a put_page(newpage) and set newpage = NULL in the main for() loop and then we may do additional put_page(newpage) after the main for loop if ret == -EEXIST, that would trigger the NULL pointer dereference. [Test case] No test case or reproducer is available at the moment, this issue has been found simply by reviewing the code. [Fix] Drop the SAUCE patch and rely on the upstream fix. [Regression potential] If the analysis is not correct we may re-introduce a page leak in cachefiles (NFS for example), but it seems unlikely to happen, since the upstream fix is addressing the page leaking already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947161] Re: ACL updates on OCFS2 are not revalidated
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
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/1947161
Title:
ACL updates on OCFS2 are not revalidated
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947161] Re: ACL updates on OCFS2 are not revalidated
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
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!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947161
Title:
ACL updates on OCFS2 are not revalidated
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
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/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
This bug is awaiting verification that the linux/5.13.0-22.22 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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-impish
** Tags added: verification-needed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947164] Re: ebpf: bpf_redirect fails with ip6 gre interfaces
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
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!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947164
Title:
ebpf: bpf_redirect fails with ip6 gre interfaces
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
The tc ebpf bpf_redirect() function cannot be used with ipv6 gre
interface.
This is fixed upstream with commit a3fa449ffcf5 ("net: handle
ARPHRD_IP6GRE in dev_is_mac_header_xmit()"), included in linux v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a3fa449ffcf5
It would probably be good to also backport this one: 3b707c3008ca
("net: dev_is_mac_header_xmit() true for ARPHRD_RAWIP").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3b707c3008ca
[Test Case]
Create an ebpf program that redirect packets to an ipv6 gre interface
and load it with tc.
[Regression Potential]
The patches are trivial, the potential regressions are low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947164/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
This bug is awaiting verification that the linux/5.13.0-22.22 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-impish ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs
This bug is awaiting verification that the linux/5.4.0-91.102 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 ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948862 Title: KVM emulation failure when booting into VM crash kernel with multiple CPUs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM emulation failure. This will cause the VM to go into the "paused" state, and prevents it from being restored without a full VM restart. This happens only when there are multiple enabled CPUs in the crash kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due to the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to access virtual addresses with a faulty MMU context that will result in the emulation failure. This shows up with a similar spew as below: $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3=290b8001 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70 71 66 0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a [Test Plan] 1. Boot an Ubuntu guest VM with e.g. multipass: $ multipass launch daily:focal -c8 -m16g -n focal-vm 2. Configure guest crash kernel command-line with `nr_cpus=8`: ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0" 3. Crash guest VM and watch for the KVM emulation failure: ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger [Where problems could occur] As we're resetting MMU context on vCPUs, potential regressions would show up in workloads relying on KVM guests. We should properly test the scenario mentioned in the bug to make sure secondary CPUs are being cleaned up properly, and that no other regressions have been introduced when rebooting or kexec'ing into different kernels. Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression potential should be fairly low and contained to starting/resetting vCPUs (i.e. VM start and reboot). [Other info] This has been fixed by upstream commit: 0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT The commit above has been picked up by stable trees up until 5.11, so it's only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two follow up commits, which revert the vendor-specific resets: 5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT 61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode() These follow ups have not been picked up in stable trees due to the risk of regressions. According to the original fix, they have been introduced primarily to aid bisection in case there are workflows relying on the vendor resets. As these are not required for the fix and don't conflict with the backport, we should leave them out to prevent potential regressions in the older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
This bug is awaiting verification that the linux/5.4.0-91.102 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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the
problem still exists, change the tag 'verification-needed-hirsute' to
'verification-failed-hirsute'.
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/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. 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-hirsute ** 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/1948470 Title: aufs: kernel bug with apparmor and fuseblk Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Invalid Status in linux source package in Jammy: Invalid Bug description: [Impact] * AppArmor-enabled applications on the aufs filesystem might hit a kernel bug when getting file attributes. * The aufs filesystem explicitly assigns a NULL pointer to `struct path.mnt` for `vfs_getattr()`, which calls into AppArmor that checks `struct path.mnt->mnt_flags`, triggering a kernel NULL pointer dereference. * This is almost 10 years old [1,2], reproducible w/ the Linux v3.2 kernel, but it's rare as apparently it needs a fuseblk mount as an aufs branch, and file creation/ open (O_CREAT), with a filename that exists only in a lower aufs branch. On Linux v5.15-rc* it doesn't need AppArmor anymore. [Fix] * The patch fixing this issue does set `struct path.mnt` properly, by taking `struct path` as parameter instead of just `struct dentry` (and making up an incomplete `struct path` w/ that `dentry` and `mnt = NULL`.) * Since it changes the signature of a key, leaf function with several callers, the patch is a bit long/refactor, but it has been tested by the upstream aufs maintainer with a private test-suite. [Test Plan] * Synthetic reproducer available in [1] and comment #1. [Regression Potential] * Regressions would probably manifest as kernel errors mostly in the lookup and open paths, but more subtle manifestations would be possible as well. * The patch modifies a fair number of functions, even if doing so in simple ways. The synthetic reproducer only covers one of those functions. * The other code paths have been tested by the maintainer w/ the mainline kernel, and should be equivalent to our kernel as none of such changed for cherry-pick/backport. * The upstream aufs maintainer runs a private test suite that covers several features and use cases of aufs, so hopefully that provides some relief to take this patch. [Other Info] * Impish no longer ships aufs; no fix needed. * Hirsute/Focal/Bionic do/need it. (H only for backports) * Hirsute/Focal are clean cherry-picks. * Bionic is a trivial backport. [1] https://sourceforge.net/p/aufs/mailman/message/37363599/ [2] https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic [Kernel Traces] BUG: kernel NULL pointer dereference, address: 0010 ... CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure #60~18.04.1-Ubuntu Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 RIP: 0010:aa_path_name+0x55/0x370 ... Call Trace: ? request_wait_answer+0xc4/0x200 path_name+0x60/0xe0 profile_path_perm.part.9+0x57/0xa0 aa_path_perm+0xe2/0x130 common_perm+0x59/0x130 common_perm_cond+0x4c/0x70 apparmor_inode_getattr+0x1d/0x20 security_inode_getattr+0x35/0x50 vfs_getattr+0x21/0x40 vfsub_update_h_iattr+0x95/0xb0 [aufs] ? lookup_dcache+0x44/0x70 ? lookup_one_len+0x66/0x90 vfsub_lookup_one_len+0x50/0x70 [aufs] au_sio_lkup_one+0x8e/0xa0 [aufs] au_lkup_dentry+0x3fa/0x660 [aufs] aufs_lookup.part.35+0x11c/0x210 [aufs] aufs_atomic_open+0xec/0x3c0 [aufs] path_openat+0xe30/0x16a0 ? aufs_lookup+0x30/0x30 [aufs] ? path_openat+0xe30/0x16a0 ? unlock_page_memcg+0x12/0x20 ? filemap_map_pages+0x17d/0x3b0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0xb2/0x170 do_sys_open+0x1ba/0x2e0 ? do_sys_open+0x1ba/0x2e0 __x64_sys_openat+0x20/0x30 do_syscall_64+0x5e/0x200 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x4a06fa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948470/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
This bug is awaiting verification that the linux/5.13.0-22.22 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-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
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-impish
** Tags added: verification-needed-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
This bug is awaiting verification that the linux/5.11.0-41.45 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-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. 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/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948862 Title: KVM emulation failure when booting into VM crash kernel with multiple CPUs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM emulation failure. This will cause the VM to go into the "paused" state, and prevents it from being restored without a full VM restart. This happens only when there are multiple enabled CPUs in the crash kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due to the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to access virtual addresses with a faulty MMU context that will result in the emulation failure. This shows up with a similar spew as below: $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log KVM internal error. Suberror: 1 emulation failure EAX=de8f EBX= ECX=008f EDX=0600 ESI= EDI= EBP= ESP=f90c EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 000f 9b00 SS =de00 000de000 9300 DS =de00 000de000 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3=290b8001 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70 71 66 0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a [Test Plan] 1. Boot an Ubuntu guest VM with e.g. multipass: $ multipass launch daily:focal -c8 -m16g -n focal-vm 2. Configure guest crash kernel command-line with `nr_cpus=8`: ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0" 3. Crash guest VM and watch for the KVM emulation failure: ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger [Where problems could occur] As we're resetting MMU context on vCPUs, potential regressions would show up in workloads relying on KVM guests. We should properly test the scenario mentioned in the bug to make sure secondary CPUs are being cleaned up properly, and that no other regressions have been introduced when rebooting or kexec'ing into different kernels. Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression potential should be fairly low and contained to starting/resetting vCPUs (i.e. VM start and reboot). [Other info] This has been fixed by upstream commit: 0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT The commit above has been picked up by stable trees up until 5.11, so it's only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two follow up commits, which revert the vendor-specific resets: 5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT 61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode() These follow ups have not been picked up in stable trees due to the risk of regressions. According to the original fix, they have been introduced primarily to aid bisection in case there are workflows relying on the vendor resets. As these are not required for the fix and don't conflict with the backport, we should leave them out to prevent potential regressions in the older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
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!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
Both eBPF and cBPF will fail as well when doing such operations.
[Test case]
$ cat bpf-mod1.c
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
static int pair[2];
static int attach()
{
int r;
struct sock_filter insn[] = {
{ BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
{ BPF_ALU | BPF_MOD, 0, 0, 1 },
{ BPF_RET | BPF_A, 0, 0, 0 },
};
struct sock_fprog prog = {};
prog.filter = insn;
prog.len = ARRAY_SIZE(insn);
socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
return 0;
}
int main(int argc, char **argv)
{
int buf[5];
int r;
r = attach();
if (r < 0) {
err(1, "function will error out already");
}
write(pair[0], "hello", 5);
r = recv(pair[1], buf, 5, MSG_DONTWAIT);
if (r != -1 || errno != EAGAIN) {
err(1, "program failed");
}
return 0;
}
$ gcc -o bpf-mod1 bpf-mod1.c
$ ./bpf-mod1
cbpf-mod1: program failed: Success
After fix:
$ ./bpf-mod1
$ echo $?
0
[Potential regression]
BPF programs might be misbehave on ppc64el.
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be
determined.
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk
This bug is awaiting verification that the linux/4.15.0-163.171 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948470 Title: aufs: kernel bug with apparmor and fuseblk Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Invalid Status in linux source package in Jammy: Invalid Bug description: [Impact] * AppArmor-enabled applications on the aufs filesystem might hit a kernel bug when getting file attributes. * The aufs filesystem explicitly assigns a NULL pointer to `struct path.mnt` for `vfs_getattr()`, which calls into AppArmor that checks `struct path.mnt->mnt_flags`, triggering a kernel NULL pointer dereference. * This is almost 10 years old [1,2], reproducible w/ the Linux v3.2 kernel, but it's rare as apparently it needs a fuseblk mount as an aufs branch, and file creation/ open (O_CREAT), with a filename that exists only in a lower aufs branch. On Linux v5.15-rc* it doesn't need AppArmor anymore. [Fix] * The patch fixing this issue does set `struct path.mnt` properly, by taking `struct path` as parameter instead of just `struct dentry` (and making up an incomplete `struct path` w/ that `dentry` and `mnt = NULL`.) * Since it changes the signature of a key, leaf function with several callers, the patch is a bit long/refactor, but it has been tested by the upstream aufs maintainer with a private test-suite. [Test Plan] * Synthetic reproducer available in [1] and comment #1. [Regression Potential] * Regressions would probably manifest as kernel errors mostly in the lookup and open paths, but more subtle manifestations would be possible as well. * The patch modifies a fair number of functions, even if doing so in simple ways. The synthetic reproducer only covers one of those functions. * The other code paths have been tested by the maintainer w/ the mainline kernel, and should be equivalent to our kernel as none of such changed for cherry-pick/backport. * The upstream aufs maintainer runs a private test suite that covers several features and use cases of aufs, so hopefully that provides some relief to take this patch. [Other Info] * Impish no longer ships aufs; no fix needed. * Hirsute/Focal/Bionic do/need it. (H only for backports) * Hirsute/Focal are clean cherry-picks. * Bionic is a trivial backport. [1] https://sourceforge.net/p/aufs/mailman/message/37363599/ [2] https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic [Kernel Traces] BUG: kernel NULL pointer dereference, address: 0010 ... CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure #60~18.04.1-Ubuntu Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 RIP: 0010:aa_path_name+0x55/0x370 ... Call Trace: ? request_wait_answer+0xc4/0x200 path_name+0x60/0xe0 profile_path_perm.part.9+0x57/0xa0 aa_path_perm+0xe2/0x130 common_perm+0x59/0x130 common_perm_cond+0x4c/0x70 apparmor_inode_getattr+0x1d/0x20 security_inode_getattr+0x35/0x50 vfs_getattr+0x21/0x40 vfsub_update_h_iattr+0x95/0xb0 [aufs] ? lookup_dcache+0x44/0x70 ? lookup_one_len+0x66/0x90 vfsub_lookup_one_len+0x50/0x70 [aufs] au_sio_lkup_one+0x8e/0xa0 [aufs] au_lkup_dentry+0x3fa/0x660 [aufs] aufs_lookup.part.35+0x11c/0x210 [aufs] aufs_atomic_open+0xec/0x3c0 [aufs] path_openat+0xe30/0x16a0 ? aufs_lookup+0x30/0x30 [aufs] ? path_openat+0xe30/0x16a0 ? unlock_page_memcg+0x12/0x20 ? filemap_map_pages+0x17d/0x3b0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0xb2/0x170 do_sys_open+0x1ba/0x2e0 ? do_sys_open+0x1ba/0x2e0 __x64_sys_openat+0x20/0x30 do_syscall_64+0x5e/0x200 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x4a06fa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1948470] Re: aufs: kernel bug with apparmor and fuseblk
This bug is awaiting verification that the linux/5.4.0-91.102 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1948470 Title: aufs: kernel bug with apparmor and fuseblk Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Invalid Status in linux source package in Jammy: Invalid Bug description: [Impact] * AppArmor-enabled applications on the aufs filesystem might hit a kernel bug when getting file attributes. * The aufs filesystem explicitly assigns a NULL pointer to `struct path.mnt` for `vfs_getattr()`, which calls into AppArmor that checks `struct path.mnt->mnt_flags`, triggering a kernel NULL pointer dereference. * This is almost 10 years old [1,2], reproducible w/ the Linux v3.2 kernel, but it's rare as apparently it needs a fuseblk mount as an aufs branch, and file creation/ open (O_CREAT), with a filename that exists only in a lower aufs branch. On Linux v5.15-rc* it doesn't need AppArmor anymore. [Fix] * The patch fixing this issue does set `struct path.mnt` properly, by taking `struct path` as parameter instead of just `struct dentry` (and making up an incomplete `struct path` w/ that `dentry` and `mnt = NULL`.) * Since it changes the signature of a key, leaf function with several callers, the patch is a bit long/refactor, but it has been tested by the upstream aufs maintainer with a private test-suite. [Test Plan] * Synthetic reproducer available in [1] and comment #1. [Regression Potential] * Regressions would probably manifest as kernel errors mostly in the lookup and open paths, but more subtle manifestations would be possible as well. * The patch modifies a fair number of functions, even if doing so in simple ways. The synthetic reproducer only covers one of those functions. * The other code paths have been tested by the maintainer w/ the mainline kernel, and should be equivalent to our kernel as none of such changed for cherry-pick/backport. * The upstream aufs maintainer runs a private test suite that covers several features and use cases of aufs, so hopefully that provides some relief to take this patch. [Other Info] * Impish no longer ships aufs; no fix needed. * Hirsute/Focal/Bionic do/need it. (H only for backports) * Hirsute/Focal are clean cherry-picks. * Bionic is a trivial backport. [1] https://sourceforge.net/p/aufs/mailman/message/37363599/ [2] https://unix.stackexchange.com/questions/324571/docker-run-causing-kernel-panic [Kernel Traces] BUG: kernel NULL pointer dereference, address: 0010 ... CPU: 23 PID: 17623 Comm: drone-agent Not tainted 5.4.0-1058-azure #60~18.04.1-Ubuntu Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 RIP: 0010:aa_path_name+0x55/0x370 ... Call Trace: ? request_wait_answer+0xc4/0x200 path_name+0x60/0xe0 profile_path_perm.part.9+0x57/0xa0 aa_path_perm+0xe2/0x130 common_perm+0x59/0x130 common_perm_cond+0x4c/0x70 apparmor_inode_getattr+0x1d/0x20 security_inode_getattr+0x35/0x50 vfs_getattr+0x21/0x40 vfsub_update_h_iattr+0x95/0xb0 [aufs] ? lookup_dcache+0x44/0x70 ? lookup_one_len+0x66/0x90 vfsub_lookup_one_len+0x50/0x70 [aufs] au_sio_lkup_one+0x8e/0xa0 [aufs] au_lkup_dentry+0x3fa/0x660 [aufs] aufs_lookup.part.35+0x11c/0x210 [aufs] aufs_atomic_open+0xec/0x3c0 [aufs] path_openat+0xe30/0x16a0 ? aufs_lookup+0x30/0x30 [aufs] ? path_openat+0xe30/0x16a0 ? unlock_page_memcg+0x12/0x20 ? filemap_map_pages+0x17d/0x3b0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0xb2/0x170 do_sys_open+0x1ba/0x2e0 ? do_sys_open+0x1ba/0x2e0 __x64_sys_openat+0x20/0x30 do_syscall_64+0x5e/0x200 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x4a06fa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
