[Kernel-packages] [Bug 1945559] Re: Failed to start Kernel Modules and small Ubuntu resolution
@Muhammed: It may be a good idea also to try a fresh Ubuntu 18.04 installation inside a different VM (with the same exact settings as this one) to see if it has the same issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945559 Title: Failed to start Kernel Modules and small Ubuntu resolution Status in linux package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Dear Experts, I updated ubuntu from 16.04 to 18.04 in vBox 6.1. There are two issues now. 1) In the start, a message is displaying: "[Failed] Failed to start Load Kernel Modules". Please see hostnamectl command display below. 2) A small ubuntu screen displays in the middle, looks like a resolution issue. I tried VBoxVGA, VMSVGA, VBoxSVGA. For VBoxSVGA, sometimes it works and full screen displays but sometimes it doesn't. Are both 1,2 are correlated and now we can solve it? Thanks, Muhammad muhammad@gul:~$ hostnamectl Static hostname: gul Icon name: computer-vm Chassis: vm Machine ID: 9fb1265c43101e08a30348bb551096be Boot ID: 8ffe16ad10064fc094583e7b11a88c0d Virtualization: oracle Operating System: Ubuntu 18.04.6 LTS Kernel: Linux 4.15.0-160-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure/5.11.0.1018.19)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1018.19) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-azure [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 1786013] Autopkgtest regression report (linux-meta-gkeop/5.4.0.1025.28)
All autopkgtests for the newly accepted linux-meta-gkeop (5.4.0.1025.28) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) glibc/2.31-0ubuntu9.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gkeop [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 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
** Tags added: originate-from-1943204 -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released 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-firmware source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released 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 Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure/5.4.0.1060.58)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1060.58) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/470.63.01-0ubuntu0.20.04.2 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [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 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
** Tags added: originate-from-1942311 ** Tags added: originate-from-1930521 -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released 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-firmware source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released 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 Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure-5.4/5.4.0.1060.40)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1060.40) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) glibc/2.27-3ubuntu1.4 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) asic0x/1.0.1-1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Ever since I turned off the ability to manage CPU cores, these "soft lockups have been happening a lot less often. Now, it's only once or twice a week, instead of 3 - 5 times a day. Today's crash report. ** Attachment added: "prevboot-2021-10-05.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5530578/+files/prevboot-2021-10-05.txt -- 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/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) 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: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
Ok, I should have waited for the firmware upgrade before posting this. They seemed to be pretty outdated, went from FW v10.2.377.29 to v11.4.1186.4 And... drum roll. it worked. Fixed the problem. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Invalid Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+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 1942589] Re: Ubuntu 5.4.0-81 stops bnx2x loading hardware
Discussion about a fix for this in upstream: https://lkml.org/lkml/2021/9/13/432 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942589 Title: Ubuntu 5.4.0-81 stops bnx2x loading hardware Status in linux package in Ubuntu: Confirmed Bug description: Server: HPE BL460c Gen9 Network: HP FlexFabric 10Gb 2-port 536FLB Adapter (Broadcom/Qlogic Net Extreme II 10/20GBE) Using ubuntu 20.04.2 with linux kernel 5.4.0-80 all functionality worked however upon upgrades via apt to 20.04.3 which uses linux kernel 5.4.0-81, ubuntu is unable to load the drivers for the network device. Below is the output for both kernels when the system is booted. ### # Kernel 5.4.0-80 working # ### ubuntu@server:$ dmesg | grep bnx2x [6.648833] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [6.695219] bnx2x :06:00.0: msix capability found [6.719107] bnx2x :06:00.0: part number 0-0-0-0 [7.112390] bnx2x :06:00.0: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.112504] bnx2x :06:00.1: msix capability found [7.112889] bnx2x :06:00.1: part number 0-0-0-0 [7.320779] bnx2x :06:00.1: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) [7.323549] bnx2x :06:00.0 eno49: renamed from eth0 [7.343281] bnx2x :06:00.1 eno50: renamed from eth1 [ 16.321102] bnx2x :06:00.1 eno50: using MSI-X IRQs: sp 130 fp[0] 132 ... fp[7] 139 [ 16.770833] bnx2x :06:00.1 eno50: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit [ 17.136896] bnx2x :06:00.0 eno49: using MSI-X IRQs: sp 120 fp[0] 122 ... fp[7] 129 [ 17.526831] bnx2x :06:00.0 eno49: NIC Link is Up, 1 Mbps full duplex, Flow control: ON - receive & transmit ubuntu@server:$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno49: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 3: eno50: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9e:b2:88:1c:ea:40 brd ff:ff:ff:ff:ff:ff inet 10.0.0.68/24 brd 10.0.0.255 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::9cb2:88ff:fe1c:ea40/64 scope link valid_lft forever preferred_lft forever ubuntu@server:$ sudo lshw -C network *-network:0 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 logical name: eno49 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:16 memory:9400-947f memory:9480-94ff memory:9501-9501 memory:92b0-92b7 *-network:1 description: Ethernet interface product: BCM57840 NetXtreme II 10/20-Gigabit Ethernet vendor: Broadcom Inc. and subsidiaries physical id: 0.1 bus info: pci@:06:00.1 logical name: eno50 version: 11 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capacity: 10Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msix pciexpress bus_master cap_list rom ethernet physical fibre 1000bt-fd 1bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bnx2x driverversion=1.713.36-0 storm 7.13.11.0 duplex=full firmware=mbi 7.18.77 bc 7.15.80 latency=0 link=yes multicast=yes port=fibre slave=yes speed=10Gbit/s resources: irq:17 memory:9300-937f memory:9380-93ff memory:9500-9500 memory:92b8-92bf *-network description: Ethernet interface physical id: 1 logical name: bond0 serial: 9e:b2:88:1c:ea:40 size: 10Gbit/s capabilities: ethernet physical
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
Just for clarification: There are 2 DHCP servers on this segment (one in HA, actually). Both respond, and I can see both Offers in the bridge. One coming straight from the host and another one form a different host via the uplink. Neither of them reach the vm (which should receive both and choose one to answer). When the uplink is out, the one from the host gets through. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Confirmed Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1946032] [NEW] NFS client fails to mount with timeout on kernel 5.4.0-1057-aws
Public bug reported: On an Ubuntu 18.04.1 server, I mount AWS EFS filesystems with nfsv4.1 successfully on ec2 instances. Mounts work on kernel version 5.4.0-1056-aws but if i upgrade the kernel to 5.4.0-1057-aws the mounts stop working with a network timeout, due to port 111 being blocked as its not needed for nfsv4 Issue started to happen when apt daily automatically upgraded the kernel version. I reproduced by rolling back kernel version on the same instance and doing mounts successfully, then reverting to newer kernel (plus reboot) and getting the network timeout issue. Mount command is identical in all cases and follows AWS Documentation ``` sudo mount -t nfs -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport mount-target-DNS:/ ~/efs-mount-point ``` Could it be a kernel bug or misconfiguration, what can i do ? ** Affects: linux-aws-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1946032 Title: NFS client fails to mount with timeout on kernel 5.4.0-1057-aws Status in linux-aws-5.4 package in Ubuntu: New Bug description: On an Ubuntu 18.04.1 server, I mount AWS EFS filesystems with nfsv4.1 successfully on ec2 instances. Mounts work on kernel version 5.4.0-1056-aws but if i upgrade the kernel to 5.4.0-1057-aws the mounts stop working with a network timeout, due to port 111 being blocked as its not needed for nfsv4 Issue started to happen when apt daily automatically upgraded the kernel version. I reproduced by rolling back kernel version on the same instance and doing mounts successfully, then reverting to newer kernel (plus reboot) and getting the network timeout issue. Mount command is identical in all cases and follows AWS Documentation ``` sudo mount -t nfs -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport mount-target-DNS:/ ~/efs-mount-point ``` Could it be a kernel bug or misconfiguration, what can i do ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1946032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
I'm also seeing a lot of "[263380.267602] br-bond0: received packet on bond0 with own address as source address (addr:4a:e1:8f:bc:32:3d, vlan:0)" in dmesg when I add the ip manually (and it works -- but gives me these messages). I don't think how a loop could be in play here, with only 1 uplink port and 1 vm port. The customer says they have STP enable on the rest of the network and a loop outside is very unlikely. I'm ignoring this for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Confirmed Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
Looks like some game mode daemon or program, which is changing parameters for cpu frequency. Like energy performance preference was changed to balance_power. Need to find out what is that program, may be some tuning can be done there as it knows game is going to be played. Also this will be helpful to get this data, while this condition is triggered. $sudo ./turbostat --show CPU,Busy%,Bzy_MHz,TSC_MHz,GFXMHz,GFXAMHz,PkgWatt,CorWatt,GFXWatt -i 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
I tested setting ageing to 0 (suggested at some internet forums): brctl setageing br-bond0 0 No improvement. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Confirmed Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Confirmed Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
I tried the exact same things on different environments and it always works. It seems to be something related to this hardware, because it happens exactly the same on 3 machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Confirmed Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530569/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530567/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530564/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530576/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530571/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530566/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530574/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530575/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530570/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530577/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530565/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530568/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530572/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530573/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
apport information ** Tags added: apport-collected focal uec-images ** Description changed: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net - I'm verifying if there is firmware updates available but I doubt it. No - extra features (like FCoE, partitioning, etc.) are enabled on the card. - It's a single dual-port mezanine card. + I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq + crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-21 (13 days ago) + InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + MachineType: IBM BladeCenter HS23 -[7875AC1]- + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 mgag200drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro + ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-88-generic N/A + linux-backports-modules-5.4.0-88-generic N/A + linux-firmware1.187.17 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.4.0-88-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 05/14/2014 + dmi.bios.vendor: IBM + dmi.bios.version: -[TKE140YUS-1.60]- + dmi.board.name: 00AE761 + dmi.board.vendor: IBM + dmi.chassis.asset.tag: none + dmi.chassis.type: 28 + dmi.chassis.vendor: IBM + dmi.chassis.version: none + dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: + dmi.product.family: System X + dmi.product.name: BladeCenter HS23 -[7875AC1]- + dmi.product.version: 07 + dmi.sys.vendor: IBM ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1946028/+attachment/5530563/+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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink).
[Kernel-packages] [Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
I also checked with GTA IV game -- with the new thermald performance also decreased. Average FPS for in-game benchmark drop from 53 to 42 (I run only one attempt for each thermald version) (and game became unplayable as minimum FPS in complex scenes became less than 30). GTA IV has a different CPU load pattern: while STALKER loads only one CPU core but to 100%, GTA IV looks to be multi-threaded -- it utilizes all cores but all of them partially (no one was > 50%). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] 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 1946028 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Incomplete Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor:
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
This is the bridge info: ubuntu@app2maas001p:~$ brctl show br-bond0 bridge name bridge id STP enabled interfaces br-bond08000.723488506c2c no bond0 tap864c7e54 ubuntu@app2maas001p:~$ brctl showstp br-bond0 br-bond0 bridge id 8000.723488506c2c designated root8000.723488506c2c root port 0path cost 0 max age 20.00 bridge max age20.00 hello time2.00 bridge hello time 2.00 forward delay 0.00 bridge forward delay 0.00 ageing time 300.00 hello timer 0.00 tcn timer 0.00 topology change timer 0.00 gc timer 1.32 flags bond0 (1) port id8001stateforwarding designated root8000.723488506c2c path cost 2 designated bridge 8000.723488506c2c message age timer 0.00 designated port8001forward delay timer0.00 designated cost 0hold timer 0.00 flags tap864c7e54 (2) port id8002stateforwarding designated root8000.723488506c2c path cost100 designated bridge 8000.723488506c2c message age timer 0.00 designated port8002forward delay timer0.00 designated cost 0hold timer 0.00 flags -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Incomplete Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
Iptables is empty with all ACCEPT policy. ebtables is empty with all ACCEPT policy. ufw is inactive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: Incomplete Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-21 (13 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: IBM BladeCenter HS23 -[7875AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=37c86220-68e3-45c6-b333-614ece4d7e57 ro ProcVersionSignature: User Name 5.4.0-88.99-generic 5.4.140 RelatedPackageVersions: linux-restricted-modules-5.4.0-88-generic N/A linux-backports-modules-5.4.0-88-generic N/A linux-firmware1.187.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 05/14/2014 dmi.bios.vendor: IBM dmi.bios.version: -[TKE140YUS-1.60]- dmi.board.name: 00AE761 dmi.board.vendor: IBM dmi.chassis.asset.tag: none dmi.chassis.type: 28 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBM:bvr-[TKE140YUS-1.60]-:bd05/14/2014:svnIBM:pnBladeCenterHS23-[7875AC1]-:pvr07:rvnIBM:rn00AE761:rvr:cvnIBM:ct28:cvrnone: dmi.product.family: System X dmi.product.name: BladeCenter HS23 -[7875AC1]- dmi.product.version: 07 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] Re: DHCP Offer not traversing linux bridge
This is the netplan config:
network:
ethernets:
eno1: {}
enp22s0f1: {}
bonds:
bond0:
# vlan 3801 - OAM is native (no tag)
interfaces:
- eno1
- enp22s0f1
parameters:
primary: eno1
mode: active-backup
mii-monitor-interval: 1s
mtu: 9000
bridges:
br-bond0:
addresses:
- 100.126.0.12/23
gateway4: 100.126.0.10
nameservers:
addresses:
- 172.21.12.32
- 172.21.12.62
search: [ "oam.prd.infra.sicredi.net" ]
interfaces:
- bond0
parameters:
forward-delay: 0
priority: 0
stp: false
mtu: 9000
version: 2
I tested with different MTU values with no changes to the result.
These are the interfaces in linux:
2: eno1: mtu 9000 qdisc mq master bond0
state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
3: enp22s0f1: mtu 9000 qdisc mq master
bond0 state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
6: br-bond0: mtu 9000 qdisc noqueue state UP
group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
inet 100.126.0.12/23 brd 100.126.1.255 scope global br-bond0
valid_lft forever preferred_lft forever
inet6 fe80::5018:6cff:fecf:de8a/64 scope link
valid_lft forever preferred_lft forever
32: bond0: mtu 9000 qdisc noqueue
master br-bond0 state UP group default qlen 1000
link/ether 72:34:88:50:6c:2c brd ff:ff:ff:ff:ff:ff
39: tap864c7e54: mtu 9000 qdisc mq master
br-bond0 state UP group default qlen 1000
link/ether ba:a8:b7:fb:e1:00 brd ff:ff:ff:ff:ff:ff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1946028
Title:
DHCP Offer not traversing linux bridge
Status in linux package in Ubuntu:
Incomplete
Bug description:
I'm facing a problem in a customer where a VM plugged to a bridge will not
get DHCP responses from dhcp server running on the host or externally (the
bridge has level 2 external uplink).
Relevant information:
- focal with latest GA kernel (5.4.0-88)
- tested with HWE (5.11) and same results
- bridge is configured using netplan, with bond as uplink, ip on the bridge
- removed bond from the equation (bridge --> eno1), same result
- host can access external network with no problems using the uplink plugged
in the bridge
- dhcp server (ISC-DHCP) configured on the host
- stp on the bridge is disabled
Create VM, attach it to the bridge, power it on, boots. Requests IP
via DHCP. The discover can be seen on tcpdump inside the vm, and also
on the tcpdump on the host bridge. DHCP server answers with Offer,
that packet can be seen in the bridge but do not enter the VM.
If I manually put an IP on the VM, it pings the host and the external
world. Mac/ARP resolution seems to be working both ways (arping
tested).
Now, if I UNPLUG the uplink from the bridge (leaving only the host
itself with IP on the bridge and one VM plugged on it) then the VM can
get IP via DHCP, the Offer comes in. I'm not sure why it matters
having the uplink when dhcp requests are being answered locally.
After being able to ping externally, if I remove the IP and try DHCP
again, it fails again.
The hardware is a IBM HS23 blade with Emulex 10Gbit cards:
ubuntu@app2maas001p:~$ lspci -v | grep -i net
16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3)
(rev 03)
Kernel driver in use: be2net
Kernel modules: be2net
16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3)
(rev 03)
Kernel driver in use: be2net
Kernel modules: be2net
I'm verifying if there is firmware updates available but I doubt it. No extra
features (like FCoE, partitioning, etc.) are enabled on the card. It's a single
dual-port mezanine card.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw+ 1 root audio 116, 1 Oct 1 18:37 seq
crw-rw+ 1 root audio 116, 33 Oct 1 18:37 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-21 (13 days ago)
InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64
(20210824)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: IBM BladeCenter HS23 -[7875AC1]-
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic
[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI
** Changed in: amd Status: New => Fix Committed -- 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/1944382 Title: Enable runtime power management for yellow carp XHCI Status in amd: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: Alex Hung 7:01 PM (1 minute ago) to kernel-team BugLink: https://bugs.launchpad.net/bugs/1944382 [Impact] XHCI controllers of yellow carp by default will not use runtime PM [Fix] Add PCI Device IDs to enable runtime PM The patch can be found @ https://patchwork.kernel.org/project/linux- usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/ [Test] This is requested and tested by AMD as described in LP:1944382 [Where problems could occur] Low risk. This only affects devices of AMD's Yellow Carp. == original descriptions == Like all XHCI controllers yellow carp XHCI by default will not use runtime PM and needs to be added to an allow list. AMD has validated that XHCI runtime PM is safe. Please include https://lore.kernel.org/linux- usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in OEM-5.14 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946028] [NEW] DHCP Offer not traversing linux bridge
Public bug reported: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. ** 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/1946028 Title: DHCP Offer not traversing linux bridge Status in linux package in Ubuntu: New Bug description: I'm facing a problem in a customer where a VM plugged to a bridge will not get DHCP responses from dhcp server running on the host or externally (the bridge has level 2 external uplink). Relevant information: - focal with latest GA kernel (5.4.0-88) - tested with HWE (5.11) and same results - bridge is configured using netplan, with bond as uplink, ip on the bridge - removed bond from the equation (bridge --> eno1), same result - host can access external network with no problems using the uplink plugged in the bridge - dhcp server (ISC-DHCP) configured on the host - stp on the bridge is disabled Create VM, attach it to the bridge, power it on, boots. Requests IP via DHCP. The discover can be seen on tcpdump inside the vm, and also on the tcpdump on the host bridge. DHCP server answers with Offer, that packet can be seen in the bridge but do not enter the VM. If I manually put an IP on the VM, it pings the host and the external world. Mac/ARP resolution seems to be working both ways (arping tested). Now, if I UNPLUG the uplink from the bridge (leaving only the host itself with IP on the bridge and one VM plugged on it) then the VM can get IP via DHCP, the Offer comes in. I'm not sure why it matters having the uplink when dhcp requests are being answered locally. After being able to ping externally, if I remove the IP and try DHCP again, it fails again. The hardware is a IBM HS23 blade with Emulex 10Gbit cards: ubuntu@app2maas001p:~$ lspci -v | grep -i net 16:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net 16:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 03) Kernel driver in use: be2net Kernel modules: be2net I'm verifying if there is firmware updates available but I doubt it. No extra features (like FCoE, partitioning, etc.) are enabled on the card. It's a single dual-port mezanine card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946024] [NEW] Focal update: v5.4.146 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.146 upstream stable release
from git://git.kernel.org/
locking/mutex: Fix HANDOFF condition
regmap: fix the offset of register error log
crypto: mxs-dcp - Check for DMA mapping errors
sched/deadline: Fix reset_on_fork reporting of DL tasks
power: supply: axp288_fuel_gauge: Report register-address on readb / writeb
errors
crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop()
sched/deadline: Fix missing clock update in migrate_task_rq_dl()
rcu/tree: Handle VM stoppage in stall detection
hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()
hrtimer: Ensure timerfd notification for HIGHRES=n
udf: Check LVID earlier
udf: Fix iocharset=utf8 mount option
isofs: joliet: Fix iocharset=utf8 mount option
bcache: add proper error unwinding in bcache_device_init
nvme-tcp: don't update queue count when failing to set io queues
nvme-rdma: don't update queue count when failing to set io queues
nvmet: pass back cntlid on successful completion
power: supply: max17042_battery: fix typo in MAx17042_TOFF
s390/cio: add dev_busid sysfs entry for each subchannel
libata: fix ata_host_start()
crypto: qat - do not ignore errors from enable_vf2pf_comms()
crypto: qat - handle both source of interrupt in VF ISR
crypto: qat - fix reuse of completion variable
crypto: qat - fix naming for init/shutdown VF to PF notifications
crypto: qat - do not export adf_iov_putmsg()
fcntl: fix potential deadlock for _struct.fa_lock
udf_get_extendedattr() had no boundary checks.
s390/kasan: fix large PMD pages address alignment check
s390/debug: fix debug area life cycle
m68k: emu: Fix invalid free in nfeth_cleanup()
sched: Fix UCLAMP_FLAG_IDLE setting
spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config
spi: spi-pic32: Fix issue with uninitialized dma_slave_config
genirq/timings: Fix error return code in irq_timings_test_irqs()
lib/mpi: use kcalloc in mpi_resize
clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock
source channel
crypto: qat - use proper type for vf_mask
certs: Trigger creation of RSA module signing key if it's not an RSA key
regulator: vctrl: Use locked regulator_get_voltage in probe path
regulator: vctrl: Avoid lockdep warning in enable/disable ops
spi: sprd: Fix the wrong WDG_LOAD_VAL
spi: spi-zynq-qspi: use wait_for_completion_timeout to make
zynq_qspi_exec_mem_op not interruptible
EDAC/i10nm: Fix NVDIMM detection
drm/panfrost: Fix missing clk_disable_unprepare() on error in
panfrost_clk_init()
media: TDA1997x: enable EDID support
soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally
media: cxd2880-spi: Fix an error handling path
bpf: Fix a typo of reuseport map in bpf.h.
bpf: Fix potential memleak and UAF in the verifier.
ARM: dts: aspeed-g6: Fix HVI3C function-group in pinctrl dtsi
arm64: dts: renesas: r8a77995: draak: Remove bogus adv7511w properties
soc: qcom: rpmhpd: Use corner in power_off
media: dvb-usb: fix uninit-value in dvb_usb_adapter_dvb_init
media: dvb-usb: fix uninit-value in vp702x_read_mac_addr
media: dvb-usb: Fix error handling in dvb_usb_i2c_init
media: go7007: remove redundant initialization
media: coda: fix frame_mem_ctrl for YUV420 and YVU420 formats
Bluetooth: sco: prevent information leak in sco_conn_defer_accept()
6lowpan: iphc: Fix an off-by-one check of array index
netns: protect netns ID lookups with RCU
drm/amdgpu/acp: Make PM domain really work
tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos
ARM: dts: meson8: Use a higher default GPU clock frequency
ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties
ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties
ARM: dts: meson8b: ec100: Fix the pwm regulator supply properties
net/mlx5e: Prohibit inner indir TIRs in IPoIB
cgroup/cpuset: Fix a partition bug with hotplug
net: cipso: fix warnings in netlbl_cipsov4_add_std
i2c: highlander: add IRQ check
leds: lt3593: Put fwnode in any case during ->probe()
leds: trigger: audio: Add an activate callback to ensure the initial brightness
is set
media: em28xx-input: fix refcount bug in em28xx_usb_disconnect
media: venus: venc: Fix potential null pointer dereference on pointer fmt
PCI: PM: Avoid forcing PCI_D0 for wakeup reasons inconsistently
PCI: PM: Enable PME if it can be signaled from D3cold
soc: qcom: smsm: Fix missed interrupts if state changes while masked
debugfs: Return error during {full/open}_proxy_open() on rmmod
Bluetooth: increase BTNAMSIZ to 21 chars to fix potential buffer overflow
PM: EM: Increase
[Kernel-packages] [Bug 1910527] Re: Cannot open URL in Evince (AppArmor issue ?)
*** This bug is a duplicate of bug 1891338 *** https://bugs.launchpad.net/bugs/1891338 ** This bug has been marked a duplicate of bug 1891338 apparmor misconfigured for evince -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910527 Title: Cannot open URL in Evince (AppArmor issue ?) Status in linux package in Ubuntu: Confirmed Bug description: Hello, In a pdf (created with Libre Office, URL checked and working), when I try to open a URL (including the one in "About Evince" to the Website), it doesn't work and the following message appears : Failed to launch preferred application for category WebBrowser. Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-1/exo- helper-2" (Permission denied) I reported this bug to Evince (https://gitlab.gnome.org/GNOME/evince/-/issues/1539#note_999642) and someone told me : "The issue you describe is likely a constraint defined at the system level, for example, using AppArmor. The issue should be reported to the distribution." Xubuntu 20.04, evince 3.36.7 Have a nice day and thanks for your amazing job ! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-17 (204 days ago) InstallationMedia: MachineType: Dell Inc. OptiPlex 9010 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=4ebde411-6fd1-4a30-b880-a931cb3c9d0e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-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: 03/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0F3KHR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/27/2013:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0F3KHR:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-17T14:44:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945367] Re: [nvidia] Graphics freeze
Hello, Since the last message, i have : - Install KDE Desktop - Modify parameters Xrender, OpenGL2.0, OpenGL3.0 - Try to install Nvidia drivers 470, NVIDIA drivers 460 Unfortunately, I encounter always the freeze of the screen in each configuration and i have to reboot my pc to get back the hand (or connect with ssh from an other pc to do a reboot). I'm joining 3 reports of breakdown, two with nvidia drivers 460 and one with nvidia drivers version 470. (with command : journalctl -b-1 > prevboot.txt) Thank you for help ** Attachment added: "Report.tar.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945367/+attachment/5530560/+files/Report.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945367 Title: [nvidia] Graphics freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the application dont give me the hand to finish the report. When i try to execute nvidia-bug-report, i have the same thing. To use the PC, i have to use nouveau drivers and intel Xe GPU with poor performances ... Thanks for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Tue Sep 28 21:13:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] InstallationDate: Installed on 2021-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Intel(R) Client Systems NUC11PHi7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: PHTGL579.0063.2021.0707.1057 dmi.board.name: NUC11PHBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M26151-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 12.19 dmi.modalias: dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: PH dmi.product.name: NUC11PHi7 dmi.product.sku: SWNUC11PHKi7C00 dmi.product.version: M26149-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1054.57~18.04.19)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1054.57~18.04.19) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [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 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1058.41)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1058.41) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64, arm64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-aws-5.4 [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 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1025.26~18.04.26)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1025.26~18.04.26) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [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 1945987] Re: linux: btrfs: fix NULL pointer dereference when deleting device by invalid id
** Changed in: linux-hwe-5.8 (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1945987
Title:
linux: btrfs: fix NULL pointer dereference when deleting device by
invalid id
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure-5.8 package in Ubuntu:
Invalid
Status in linux-hwe-5.8 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure-5.8 source package in Focal:
In Progress
Status in linux-hwe-5.8 source package in Focal:
Fix Committed
Bug description:
[BUG]
It's easy to trigger NULL pointer dereference, just by removing a
non-existing device id:
# mkfs.btrfs -f -m single -d single /dev/test/scratch1 \
/dev/test/scratch2
# mount /dev/test/scratch1 /mnt/btrfs
# btrfs device remove 3 /mnt/btrfs
Then we have the following kernel NULL pointer dereference:
BUG: kernel NULL pointer dereference, address:
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 0 P4D 0
Oops: [#1] PREEMPT SMP NOPTI
CPU: 9 PID: 649 Comm: btrfs Not tainted 5.14.0-rc3-custom+ #35
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:btrfs_rm_device+0x4de/0x6b0 [btrfs]
btrfs_ioctl+0x18bb/0x3190 [btrfs]
? lock_is_held_type+0xa5/0x120
? find_held_lock.constprop.0+0x2b/0x80
? do_user_addr_fault+0x201/0x6a0
? lock_release+0xd2/0x2d0
? __x64_sys_ioctl+0x83/0xb0
__x64_sys_ioctl+0x83/0xb0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
[CAUSE]
Commit a27a94c2b0c7 ("btrfs: Make btrfs_find_device_by_devspec return
btrfs_device directly") moves the "missing" device path check into
btrfs_rm_device().
But btrfs_rm_device() itself can have case where it only receives
@devid, with NULL as @device_path.
In that case, calling strcmp() on NULL will trigger the NULL pointer
dereference.
Before that commit, we handle the "missing" case inside
btrfs_find_device_by_devspec(), which will not check @device_path at all
if @devid is provided, thus no way to trigger the bug.
[FIX]
Before calling strcmp(), also make sure @device_path is not NULL.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1945987/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Changed in: linux-hwe-5.8 (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-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
** Changed in: linux-hwe-5.8 (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-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains asymmetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html * Previous reviews Unstable & v5.13: https://lists.ubuntu.com/archives/kernel- team/2021-June/121362.html Hirsute & v5.11: https://lists.ubuntu.com/archives/kernel- team/2021-August/122996.html Focal & v5.10 (oem): https://lists.ubuntu.com/archives/kernel- team/2021-August/123470.html Focal & v5.8 (azure): https://lists.ubuntu.com/archives/kernel- team/2021-September/124336.html Focal & v5.4: https://lists.ubuntu.com/archives/kernel- team/2021-October/124497.html Bionic & v4.15: TODO Xenial & v4.4: TODO Trusty & v3.13: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.8 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-hwe-5.8 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-hwe-5.8 (Ubuntu Hirsute) 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/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains asymmetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html * Previous reviews Unstable & v5.13: https://lists.ubuntu.com/archives/kernel- team/2021-June/121362.html Hirsute & v5.11: https://lists.ubuntu.com/archives/kernel- team/2021-August/122996.html Focal & v5.10 (oem): https://lists.ubuntu.com/archives/kernel- team/2021-August/123470.html Focal & v5.8 (azure): https://lists.ubuntu.com/archives/kernel- team/2021-September/124336.html Focal & v5.4: https://lists.ubuntu.com/archives/kernel- team/2021-October/124497.html Bionic & v4.15: TODO Xenial & v4.4: TODO Trusty & v3.13: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
balance_power is not a kernel default, so something on the system running which is changing cpufreq parameters. "balamce_performance" is the default. Anyway thermald is setting the package power limit as per thermal tables. There is no power sharing info in the tables. We have this power sharing gap, which needs to be addressed. I thought it will be as simple as setting these knobs. But since they don't help, need to try other methods. I will try to setup the game and check. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945559] Re: Failed to start Kernel Modules and small Ubuntu resolution
I'm marking this invalid for the ubuntu-advantage-tools package since this bug appears unrelated. ** Changed in: ubuntu-advantage-tools (Ubuntu) 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/1945559 Title: Failed to start Kernel Modules and small Ubuntu resolution Status in linux package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Invalid Bug description: Dear Experts, I updated ubuntu from 16.04 to 18.04 in vBox 6.1. There are two issues now. 1) In the start, a message is displaying: "[Failed] Failed to start Load Kernel Modules". Please see hostnamectl command display below. 2) A small ubuntu screen displays in the middle, looks like a resolution issue. I tried VBoxVGA, VMSVGA, VBoxSVGA. For VBoxSVGA, sometimes it works and full screen displays but sometimes it doesn't. Are both 1,2 are correlated and now we can solve it? Thanks, Muhammad muhammad@gul:~$ hostnamectl Static hostname: gul Icon name: computer-vm Chassis: vm Machine ID: 9fb1265c43101e08a30348bb551096be Boot ID: 8ffe16ad10064fc094583e7b11a88c0d Virtualization: oracle Operating System: Ubuntu 18.04.6 LTS Kernel: Linux 4.15.0-160-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI
I checked this on YC and it works properly. ** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1944382 Title: Enable runtime power management for yellow carp XHCI Status in amd: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: Alex Hung 7:01 PM (1 minute ago) to kernel-team BugLink: https://bugs.launchpad.net/bugs/1944382 [Impact] XHCI controllers of yellow carp by default will not use runtime PM [Fix] Add PCI Device IDs to enable runtime PM The patch can be found @ https://patchwork.kernel.org/project/linux- usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/ [Test] This is requested and tested by AMD as described in LP:1944382 [Where problems could occur] Low risk. This only affects devices of AMD's Yellow Carp. == original descriptions == Like all XHCI controllers yellow carp XHCI by default will not use runtime PM and needs to be added to an allow list. AMD has validated that XHCI runtime PM is safe. Please include https://lore.kernel.org/linux- usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in OEM-5.14 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945559] Re: Failed to start Kernel Modules and small Ubuntu resolution
This cannot be answered with the information currently available. The problems might be caused from either side of the VM (the host or the guest). What OS/version is the host running? What exact version of Virtualbox? 6.1 might be anything from Ubuntu 20.04 onward. Which modules fail to load. For more information about the guest you should run "apport-collect 1945559" inside the guest (assuming the guess can connect to the internet). ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945559 Title: Failed to start Kernel Modules and small Ubuntu resolution Status in linux package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: New Bug description: Dear Experts, I updated ubuntu from 16.04 to 18.04 in vBox 6.1. There are two issues now. 1) In the start, a message is displaying: "[Failed] Failed to start Load Kernel Modules". Please see hostnamectl command display below. 2) A small ubuntu screen displays in the middle, looks like a resolution issue. I tried VBoxVGA, VMSVGA, VBoxSVGA. For VBoxSVGA, sometimes it works and full screen displays but sometimes it doesn't. Are both 1,2 are correlated and now we can solve it? Thanks, Muhammad muhammad@gul:~$ hostnamectl Static hostname: gul Icon name: computer-vm Chassis: vm Machine ID: 9fb1265c43101e08a30348bb551096be Boot ID: 8ffe16ad10064fc094583e7b11a88c0d Virtualization: oracle Operating System: Ubuntu 18.04.6 LTS Kernel: Linux 4.15.0-160-generic Architecture: x86-64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946001] [NEW] impish:linux-aws 5.13 panic during systemd autotest
Public bug reported: Found this when running the systemd autopkgtest on linux-aws 5.13.0-1004.5 (apparently it seems to affect nested kvm only): systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI [ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 5.13.0-1004-aws #5-Ubuntu [ 70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [ 70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.239670] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.239679] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.239688] R10: R11: R12: 97e8411da400 [ 70.239696] R13: 97e8411da400 R14: 0cc0 R15: b2737cf0 [ 70.239705] FS: 7fc6fc243380() GS:97e85c00() knlGS: [ 70.239713] CS: 0010 DS: ES: CR0: 80050033 [ 70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 06f0 [ 70.239727] Call Trace: [ 70.239733] getname_flags.part.0+0x30/0x1b0 [ 70.239741] getname+0x35/0x50 [ 70.239746] do_sys_openat2+0x64/0x150 [ 70.239753] __x64_sys_openat+0x55/0x90 [ 70.239759] do_syscall_64+0x61/0xb0 [ 70.239766] ? do_syscall_64+0x6e/0xb0 [ 70.239772] ? do_sync_core+0x26/0x30 [ 70.239779] ? flush_smp_call_function_queue+0x119/0x190 [ 70.239786] ? exit_to_user_mode_prepare+0x37/0xb0 [ 70.239793] ? irqentry_exit_to_user_mode+0x9/0x20 [ 70.239800] ? irqentry_exit+0x19/0x30 [ 70.239807] ? sysvec_call_function+0x4e/0x90 [ 70.239813] ? asm_sysvec_call_function+0xa/0x20 [ 70.239819] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 70.239826] RIP: 0033:0x7fc6fca946e4 [ 70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4 [ 70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 0101 [ 70.240063] RAX: ffda RBX: RCX: 7fc6fca946e4 [ 70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: ff9c [ 70.240085] RBP: 556e8d5885d0 R08: R09: [ 70.240095] R10: R11: 0293 R12: 00080802 [ 70.240104] R13: R14: 556e8d59dd90 R15: fffa [ 70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy [ 70.281001] ---[ end trace 044cf87b8c867a36 ]--- [ 70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.281138] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.281143] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.281148] R10: R11: R12: 97e8411da400 [ 70.281154] R13: 97e8411da400 R14: 0cc0 R15: b2737cf0 [ 70.281159] FS: 7fc6fc243380() GS:97e85c00() knlGS: [ 70.281173] CS: 0010 DS: ES: CR0: 80050033 [ 70.281178] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 06f0 [ 70.281183] Kernel panic - not syncing: Fatal exception in interrupt [ 70.282418] Kernel Offset: 0x3140 from 0x8100 (relocation range: 0x8000-0xbfff) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New ** Package changed: linux-oem-5.6 (Ubuntu) => linux-aws (Ubuntu) ** Also affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New ** Description changed: - Found this when running the systemd autopkgtest (apparently it seems to - affect nested kvm only): + Found this when running the systemd autopkgtest on linux-aws + 5.13.0-1004.5 (apparently it seems to affect nested kvm only): systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI [ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 5.13.0-1004-aws #5-Ubuntu [ 70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [ 70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb
[Kernel-packages] [Bug 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from impish
** Also affects: dwarves-dfsg (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libbpf (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: dwarves-dfsg (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libbpf in Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.21 from impish Status in dwarves-dfsg package in Ubuntu: Invalid Status in libbpf package in Ubuntu: Fix Released Status in dwarves-dfsg source package in Bionic: In Progress Status in libbpf source package in Bionic: New Status in dwarves-dfsg source package in Focal: Fix Committed Status in libbpf source package in Focal: Won't Fix Status in dwarves-dfsg source package in Groovy: Won't Fix Status in libbpf source package in Groovy: Won't Fix Status in dwarves-dfsg source package in Hirsute: Fix Committed Status in libbpf source package in Hirsute: Won't Fix Bug description: [Impact] BTF is an extremely useful tool for BPF developers. Enabling BTF support in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but in focal we have only 1.15. The simplest path for us to get a sufficiently updated version of pahole is to backport dwarves-dfsg from hirsute, which is at version 1.21 with v5.13 compat fixes. [Test Case] Building a v5.13 based kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the version of pahole currently in focal, complaining that pahole 1.16 or later is needed. Building with a newer version of pahole is successful. [Where problems could occur] Moving the package forward carries significant risks. The biggest risk is clearly new bugs. There may also be interface changes which break existing workflows. I believe the following factors indicate that the level of risk here is acceptable: * Currently there are no bug reports open against the package in groovy (there are virtually no bug reports open at all against the package in fact). * I have done a review of the changes between 1.15 and 1.21. The bulk of the changes are for the required BTF support, and the vast majority of these are an update of its local copy of libbpf. The balance of the changes are bug fixes and enhancements to pahole, none of which look to change the user interface in a way which will break existing workflows. Note that in later releases libbpf is now packaged stand alone, so this SRU covers libbpf as well. * But also the 1.15 dwarves is kind of useless, as it doesn't work with latest kernels for the BPF features. * No packages in focal have dependencies or build dependencies on the dwarves package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945987] Re: linux: btrfs: fix NULL pointer dereference when deleting device by invalid id
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1945987
Title:
linux: btrfs: fix NULL pointer dereference when deleting device by
invalid id
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure-5.8 package in Ubuntu:
Invalid
Status in linux-hwe-5.8 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
In Progress
Status in linux-azure-5.8 source package in Focal:
In Progress
Status in linux-hwe-5.8 source package in Focal:
In Progress
Bug description:
[BUG]
It's easy to trigger NULL pointer dereference, just by removing a
non-existing device id:
# mkfs.btrfs -f -m single -d single /dev/test/scratch1 \
/dev/test/scratch2
# mount /dev/test/scratch1 /mnt/btrfs
# btrfs device remove 3 /mnt/btrfs
Then we have the following kernel NULL pointer dereference:
BUG: kernel NULL pointer dereference, address:
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 0 P4D 0
Oops: [#1] PREEMPT SMP NOPTI
CPU: 9 PID: 649 Comm: btrfs Not tainted 5.14.0-rc3-custom+ #35
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:btrfs_rm_device+0x4de/0x6b0 [btrfs]
btrfs_ioctl+0x18bb/0x3190 [btrfs]
? lock_is_held_type+0xa5/0x120
? find_held_lock.constprop.0+0x2b/0x80
? do_user_addr_fault+0x201/0x6a0
? lock_release+0xd2/0x2d0
? __x64_sys_ioctl+0x83/0xb0
__x64_sys_ioctl+0x83/0xb0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
[CAUSE]
Commit a27a94c2b0c7 ("btrfs: Make btrfs_find_device_by_devspec return
btrfs_device directly") moves the "missing" device path check into
btrfs_rm_device().
But btrfs_rm_device() itself can have case where it only receives
@devid, with NULL as @device_path.
In that case, calling strcmp() on NULL will trigger the NULL pointer
dereference.
Before that commit, we handle the "missing" case inside
btrfs_find_device_by_devspec(), which will not check @device_path at all
if @devid is provided, thus no way to trigger the bug.
[FIX]
Before calling strcmp(), also make sure @device_path is not NULL.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1945987/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945989] 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 1945989 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 ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS or other certs and justify why a commit was kept or removed. To simplify this process we can add an automated check that will abort the kernel preparation and build when such changes exist without a justification. [Test Plan] Check if the kernel preparation fails (cranky close) when one of a security certification changes is added. [Where problems could occur] No kernels should be affected until we enable this check on each one. Even when enabled, that only affects the kernel preparation and not the resulting kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945989] [NEW] Check for changes relevant for security certifications
Public bug reported: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS or other certs and justify why a commit was kept or removed. To simplify this process we can add an automated check that will abort the kernel preparation and build when such changes exist without a justification. [Test Plan] Check if the kernel preparation fails (cranky close) when one of a security certification changes is added. [Where problems could occur] No kernels should be affected until we enable this check on each one. Even when enabled, that only affects the kernel preparation and not the resulting kernel. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Summary changed: - Check for changes relevant for security certification + Check for changes relevant for security certifications -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Impish: New Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS or other certs and justify why a commit was kept or removed. To simplify this process we can add an automated check that will abort the kernel preparation and build when such changes exist without a justification. [Test Plan] Check if the kernel preparation fails (cranky close) when one of a security certification changes is added. [Where problems could occur] No kernels should be affected until we enable this check on each one. Even when enabled, that only affects the kernel preparation and not the resulting kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945987] [NEW] linux: btrfs: fix NULL pointer dereference when deleting device by invalid id
Public bug reported:
[BUG]
It's easy to trigger NULL pointer dereference, just by removing a
non-existing device id:
# mkfs.btrfs -f -m single -d single /dev/test/scratch1 \
/dev/test/scratch2
# mount /dev/test/scratch1 /mnt/btrfs
# btrfs device remove 3 /mnt/btrfs
Then we have the following kernel NULL pointer dereference:
BUG: kernel NULL pointer dereference, address:
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 0 P4D 0
Oops: [#1] PREEMPT SMP NOPTI
CPU: 9 PID: 649 Comm: btrfs Not tainted 5.14.0-rc3-custom+ #35
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:btrfs_rm_device+0x4de/0x6b0 [btrfs]
btrfs_ioctl+0x18bb/0x3190 [btrfs]
? lock_is_held_type+0xa5/0x120
? find_held_lock.constprop.0+0x2b/0x80
? do_user_addr_fault+0x201/0x6a0
? lock_release+0xd2/0x2d0
? __x64_sys_ioctl+0x83/0xb0
__x64_sys_ioctl+0x83/0xb0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
[CAUSE]
Commit a27a94c2b0c7 ("btrfs: Make btrfs_find_device_by_devspec return
btrfs_device directly") moves the "missing" device path check into
btrfs_rm_device().
But btrfs_rm_device() itself can have case where it only receives
@devid, with NULL as @device_path.
In that case, calling strcmp() on NULL will trigger the NULL pointer
dereference.
Before that commit, we handle the "missing" case inside
btrfs_find_device_by_devspec(), which will not check @device_path at all
if @devid is provided, thus no way to trigger the bug.
[FIX]
Before calling strcmp(), also make sure @device_path is not NULL.
** Affects: linux-azure-5.8 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-hwe-5.8 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-azure-5.8 (Ubuntu Focal)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-hwe-5.8 (Ubuntu Focal)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Also affects: linux-hwe-5.8 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-hwe-5.8 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: New => Invalid
** Also affects: linux-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.8 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-azure-5.8 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-azure-5.8 (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure-5.8 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1945987
Title:
linux: btrfs: fix NULL pointer dereference when deleting device by
invalid id
Status in linux-azure-5.8 package in Ubuntu:
Invalid
Status in linux-hwe-5.8 package in Ubuntu:
Invalid
Status in linux-azure-5.8 source package in Focal:
In Progress
Status in linux-hwe-5.8 source package in Focal:
In Progress
Bug description:
[BUG]
It's easy to trigger NULL pointer dereference, just by removing a
non-existing device id:
# mkfs.btrfs -f -m single -d single /dev/test/scratch1 \
/dev/test/scratch2
# mount /dev/test/scratch1 /mnt/btrfs
# btrfs device remove 3 /mnt/btrfs
Then we have the following kernel NULL pointer dereference:
BUG: kernel NULL pointer dereference, address:
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 0 P4D 0
Oops: [#1] PREEMPT SMP NOPTI
CPU: 9 PID: 649 Comm: btrfs Not tainted 5.14.0-rc3-custom+ #35
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:btrfs_rm_device+0x4de/0x6b0 [btrfs]
btrfs_ioctl+0x18bb/0x3190 [btrfs]
? lock_is_held_type+0xa5/0x120
? find_held_lock.constprop.0+0x2b/0x80
? do_user_addr_fault+0x201/0x6a0
? lock_release+0xd2/0x2d0
? __x64_sys_ioctl+0x83/0xb0
__x64_sys_ioctl+0x83/0xb0
do_syscall_64+0x3b/0x90
entry_SYSCALL_64_after_hwframe+0x44/0xae
[CAUSE]
Commit a27a94c2b0c7 ("btrfs: Make btrfs_find_device_by_devspec return
btrfs_device directly") moves the "missing" device path check into
btrfs_rm_device().
But btrfs_rm_device() itself can have case where it only receives
@devid, with NULL as @device_path.
In that case, calling strcmp() on NULL will trigger the NULL pointer
dereference.
Before that commit, we handle the "missing" case inside
[Kernel-packages] [Bug 1945985] [NEW] Can't use number pad for password prompt full disk encryption
Public bug reported: When the entering my password for full disk encryption, I cannot use the number pad to enter numbers. The number pad keys enter several characters in the password prompt and that occasionally makes the password prompt crash. Entering the numbers using the top keyboard row has no problems. Ubuntu 20.04.3 LTS 5.11.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 09:08:23 2021 InstallationDate: Installed on 2021-07-30 (65 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945985 Title: Can't use number pad for password prompt full disk encryption Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: When the entering my password for full disk encryption, I cannot use the number pad to enter numbers. The number pad keys enter several characters in the password prompt and that occasionally makes the password prompt crash. Entering the numbers using the top keyboard row has no problems. Ubuntu 20.04.3 LTS 5.11.0-37-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 4 09:08:23 2021 InstallationDate: Installed on 2021-07-30 (65 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1945985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874186] Re: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout
On F-5.4 KVM it took about 3m40s to run through all 142218 tests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1874186 Title: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Invalid Bug description: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874186] Re: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout
** Summary changed: - vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests timeout on E-KVM + vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1874186 Title: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Invalid Bug description: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831449] Re: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT)
When comparing the Focal 5.4 generic AMD64 kernel test output and Focal 5.4 KVM AMD64 kernel test output, you can see the generic kernel will pass with: PASS: clflush (present) PASS: sfence (present) PASS: lfence (present) PASS: mfence (present) PASS: clflushopt (ABSENT) PASS: clwb (ABSENT) PASS: invalid clwb PASS: pcommit (ABSENT) SUMMARY: 8 tests PASS memory (8 tests) Instead the KVM kernel will fail with: FAIL: clflushopt (ABSENT) FAIL: clwb (ABSENT) I wonder what's the difference here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests fails (clflushopt / clwb ABSENT) Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: FAIL: clflushopt (ABSENT) FAIL: clwb (ABSENT) Test output: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory' BUILD_HEAD=32db322d timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.SOyUkPCNxP -smp 1 -cpu max # -initrd /tmp/tmp.DiAWwvk2jC enabling apic PASS: clflush (present) PASS: sfence (present) PASS: lfence (present) PASS: mfence (present) FAIL: clflushopt (ABSENT) FAIL: clwb (ABSENT) PASS: invalid clwb PASS: pcommit (ABSENT) SUMMARY: 8 tests, 2 unexpected failures FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute
Without this multiplier, this can be spotted on H-gcp-5.11 / F-gcp-5.4 with g1.small Testing with uncommitted changes on obruchev / garlog. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 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: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
Hi All,
Please try with the EnableBrightnessControl =1 as kernel parameter or add it in
xorg.conf file.
You can add it in device section as shown below -
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "NVIDIA RTX A3000 Laptop GPU"
Option "RegistryDwords" "EnableBrightnessControl=1"
EndSection
After change in the xorg, please uninstall / install the driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
Document provided by Intel: https://www.kernel.org/doc/html/latest/hid/intel-ish-hid.html Base on the document: the test steps will be: 1. Install tree: sudo apt-get install tree 2. sudo tree -l /sys/bus/iio/devices/ 3. Check if devices exited. Example on AAEON's EHL board: https://certification.canonical.com/hardware/202109-29492/ u@linux:~$ sudo tree -l /sys/bus/iio/devices/ /sys/bus/iio/devices/ └── iio:device0 -> ../../../devices/pci:00/:00:1e.2/pxa2xx-spi.10/spi_master/spi0/spi-AANT1280:00/iio:device0 ├── in_voltage0_raw ├── in_voltage1_raw ├── in_voltage2_raw ├── in_voltage3_raw ├── in_voltage_scale ├── power │ ├── async │ ├── autosuspend_delay_ms │ ├── control │ ├── runtime_active_kids │ ├── runtime_active_time │ ├── runtime_enabled │ ├── runtime_status │ ├── runtime_suspended_time │ └── runtime_usage ├── subsystem -> ../../../../../../../../bus/iio │ ├── devices │ │ └── iio:device0 -> ../../../devices/pci:00/:00:1e.2/pxa2xx-spi.10/spi_master/spi0/spi-AANT1280:00/iio:device0 [recursive, not followed] │ ├── drivers │ ├── drivers_autoprobe │ ├── drivers_probe │ └── uevent └── uevent -- 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/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will
[Kernel-packages] [Bug 1938031] Re: Focal update: 5.10.51 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51
---
linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP:
#1944209)
* e1000e extremly slow (LP: #1930754)
- SAUCE: e1000e: Separate TGP board type from SPT
- SAUCE: e1000e: Fixing packet loss issues on new platforms
* CVE-2021-41073
- io_uring: ensure symmetry in handling iter types in loop_rw_iter()
-- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021
18:33:36 +0800
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1938031
Title:
Focal update: 5.10.51 upstream stable release
Status in linux-oem-5.10 package in Ubuntu:
Confirmed
Status in linux-oem-5.10 source package in Focal:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
5.10.51 upstream stable release
from git://git.kernel.org/
Linux 5.10.51
f2fs: fix to avoid racing on fsync_entry_slab by multi filesystem instances
ext4: fix memory leak in ext4_fill_super
smackfs: restrict bytes count in smk_set_cipso()
jfs: fix GPF in diFree
drm/ast: Remove reference to struct drm_device.pdev
pinctrl: mcp23s08: Fix missing unlock on error in mcp23s08_irq()
dm writecache: write at least 4k when committing
io_uring: fix clear IORING_SETUP_R_DISABLED in wrong function
media: uvcvideo: Fix pixel format change for Elgato Cam Link 4K
media: gspca/sunplus: fix zero-length control requests
media: gspca/sq905: fix control-request direction
media: zr364xx: fix memory leak in zr364xx_start_readpipe
media: dtv5100: fix control-request directions
media: subdev: disallow ioctl for saa6588/davinci
PCI: aardvark: Implement workaround for the readback value of VEND_ID
PCI: aardvark: Fix checking for PIO Non-posted Request
PCI: Leave Apple Thunderbolt controllers on for s2idle or standby
dm btree remove: assign new_root only when removal succeeds
dm writecache: flush origin device when writing and cache is full
dm zoned: check zone capacity
coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()
coresight: Propagate symlink failure
ipack/carriers/tpci200: Fix a double free in tpci200_pci_probe
tracing: Resize tgid_map to pid_max, not PID_MAX_DEFAULT
tracing: Simplify & fix saved_tgids logic
rq-qos: fix missed wake-ups in rq_qos_throttle try two
seq_buf: Fix overflow in seq_buf_putmem_hex()
extcon: intel-mrfld: Sync hardware and software state on init
selftests/lkdtm: Fix expected text for CR4 pinning
lkdtm/bugs: XFAIL UNALIGNED_LOAD_STORE_WRITE
nvmem: core: add a missing of_node_put
mfd: syscon: Free the allocated name field of struct regmap_config
power: supply: ab8500: Fix an old bug
ubifs: Fix races between xattr_{set|get} and listxattr operations
thermal/drivers/int340x/processor_thermal: Fix tcc setting
ipmi/watchdog: Stop watchdog timer when the current action is 'none'
qemu_fw_cfg: Make fw_cfg_rev_attr a proper kobj_attribute
i40e: fix PTP on 5Gb links
ASoC: tegra: Set driver_name=tegra for all machine drivers
fpga: stratix10-soc: Add missing fpga_mgr_free() call
clocksource/arm_arch_timer: Improve Allwinner A64 timer workaround
cpu/hotplug: Cure the cpusets trainwreck
arm64: tlb: fix the TTL value of tlb_get_level
ata: ahci_sunxi: Disable DIPM
mmc: core: Allow UHS-I voltage switch for SDSC cards if supported
mmc: core: clear flags before allowing to retune
mmc: sdhci: Fix warning message when accessing RPMB in HS400 mode
mmc: sdhci-acpi: Disable write protect detection on Toshiba Encore 2 WT8-B
drm/i915/display: Do not zero past infoframes.vsc
drm/nouveau: Don't set allow_fb_modifiers explicitly
drm/arm/malidp: Always list modifiers
drm/msm/mdp4: Fix modifier support enabling
drm/tegra: Don't set allow_fb_modifiers explicitly
drm/amd/display: Reject non-zero src_y and src_x for video planes
pinctrl/amd: Add device HID for new AMD GPIO controller
drm/amd/display: fix incorrrect valid irq check
drm/rockchip: dsi: remove extra component_del() call
drm/dp: Handle zeroed port counts in drm_dp_read_downstream_info()
drm/vc4: hdmi: Prevent clock unbalance
drm/vc4: crtc: Skip the TXP
drm/vc4: txp: Properly set the possible_crtcs mask
[Kernel-packages] [Bug 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- 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/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress 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: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress 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: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938028] Re: Focal update: 5.10.49 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938028 Title: Focal update: 5.10.49 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.10.49 upstream stable release from git://git.kernel.org/ Linux 5.10.49 xen/events: reset active flag for lateeoi events later Hexagon: change jumps to must-extend in futex_atomic_* Hexagon: add target builtins to kernel Hexagon: fix build errors media: uvcvideo: Support devices that report an OT as an entity source KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1938028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] 1. On Troy JSL platform, add AC9560 2. Enter Settings -> Bluetooth menu 3. Default Bluetooth option is ON, try to toggle the BT option to OFF 4. Into suspend mode(S3) and resume the system 5. Enter BT settings and try to turn on BT, 6. BT function cannot enabled until reboot. [Fix] Turn off the msft ext only for AC9560. Maintainer thought Intel should take care this and reject this workaround. https://marc.info/?l=linux-bluetooth=162938546804458=2 Intel is working on this issue and sru the workaround for the schedule. [Test] Verified with the bellow steps 10 times. 1. On Troy JSL and add AC9560 2. Turn off BT 3. suspend the machine 10 times. 4. turn on BT and works well. [Regression Potential] Medium, it's a workaround to turn off the MSFT ext only for ac9560. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51
---
linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP:
#1944209)
* e1000e extremly slow (LP: #1930754)
- SAUCE: e1000e: Separate TGP board type from SPT
- SAUCE: e1000e: Fixing packet loss issues on new platforms
* CVE-2021-41073
- io_uring: ensure symmetry in handling iter types in loop_rw_iter()
-- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021
18:33:36 +0800
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/groovy/hirsute/impish
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
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:
Fix Committed
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 Committed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Bug description:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
not failing as expected, and thus this test will fail with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests coming from user"), we relaxed the min gso_size check in
virtio_net_hdr_to_skb().
So when a packet which is smaller then the gso_size, GSO for this
packet will not be set, the packet will be send/recv successfully.
[Fix]
* cfba3fb68960b4 selftests/net: remove min gso test in packet_snd
This patch can be cherry-picked into all affected kernels.
I decided to skip those 5.8 variants, as the current cycle
(2021-09-06) might be the last cycle for them.
[Test]
Run this psock_snd.sh script, this test will no longer exist and the
script can proceed with the next test.
[Where problems could occur]
Removing this broken test should not have any negative impact to our
tests. We will need to update our hints later.
[Original Bug Report]
Testing failed on focal/linux 5.4.0-44.48:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz
psock_snd.sh output:
16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh
16:28:31 DEBUG| [stdout] # dgram
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # dgram bind
16:28:31 DEBUG| [stdout] # tx: 128
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw bind
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw qdisc bypass
16:28:31 DEBUG| [stdout] # tx: 142
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vlan
16:28:31 DEBUG| [stdout] # tx: 146
16:28:31 DEBUG| [stdout] # rx: 100
16:28:31 DEBUG| [stdout] # OK
16:28:31 DEBUG| [stdout] #
16:28:31 DEBUG| [stdout] # raw vnet hdr
16:28:31 DEBUG| [stdout] # tx: 152
16:28:31 DEBUG| [stdout] # rx: 142
16:28:31 DEBUG| [stdout] #
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: New Status in linux-azure-5.8 source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains asymmetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html * Previous reviews Unstable & v5.13: https://lists.ubuntu.com/archives/kernel- team/2021-June/121362.html Hirsute & v5.11: https://lists.ubuntu.com/archives/kernel- team/2021-August/122996.html Focal & v5.10 (oem): https://lists.ubuntu.com/archives/kernel- team/2021-August/123470.html Focal & v5.8 (azure): https://lists.ubuntu.com/archives/kernel- team/2021-September/124336.html Focal & v5.4: https://lists.ubuntu.com/archives/kernel- team/2021-October/124497.html Bionic & v4.15: TODO Xenial & v4.4: TODO Trusty & v3.13: TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938029] Re: Focal update: 5.10.50 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938029 Title: Focal update: 5.10.50 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.10.50 upstream stable release from git://git.kernel.org/ Linux 5.10.50 powerpc/preempt: Don't touch the idle task's preempt_count during hotplug iommu/dma: Fix compile warning in 32-bit builds cred: add missing return error code when set_cred_ucounts() failed s390: preempt: Fix preempt_count initialization crypto: qce - fix error return code in qce_skcipher_async_req_handle() scsi: core: Retry I/O for Notify (Enable Spinup) Required error media: exynos4-is: remove a now unused integer mmc: vub3000: fix control-request direction mmc: block: Disable CMDQ on the ioctl path io_uring: fix blocking inline submission block: return the correct bvec when checking for gaps erofs: fix error return code in erofs_read_superblock() tpm: Replace WARN_ONCE() with dev_err_once() in tpm_tis_status() fscrypt: fix derivation of SipHash keys on big endian CPUs fscrypt: don't ignore minor_hash when hash is 0 mailbox: qcom-ipcc: Fix IPCC mbox channel exhaustion scsi: target: cxgbit: Unmap DMA buffer before calling target_execute_cmd() scsi: fc: Correct RHBA attributes length exfat: handle wrong stream entry size in exfat_readdir() csky: syscache: Fixup duplicate cache flush csky: fix syscache.c fallthrough warning perf llvm: Return -ENOMEM when asprintf() fails selftests/vm/pkeys: refill shadow register after implicit kernel write selftests/vm/pkeys: handle negative sys_pkey_alloc() return code selftests/vm/pkeys: fix alloc_random_pkey() to make it really, really random lib/math/rational.c: fix divide by zero mm/z3fold: use release_z3fold_page_locked() to release locked z3fold page mm/z3fold: fix potential memory leak in z3fold_destroy_pool() include/linux/huge_mm.h: remove extern keyword hugetlb: remove prep_compound_huge_page cleanup mm/hugetlb: remove redundant check in preparing and destroying gigantic page mm/hugetlb: use helper huge_page_order and pages_per_huge_page mm/huge_memory.c: don't discard hugepage if other processes are mapping it mm/huge_memory.c: add missing read-only THP checking in transparent_hugepage_enabled() mm/huge_memory.c: remove dedicated macro HPAGE_CACHE_INDEX_MASK mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled vfio/pci: Handle concurrent vma faults arm64: dts: marvell: armada-37xx: Fix reg for standard variant of UART serial: mvebu-uart: correctly calculate minimal possible baudrate serial: mvebu-uart: do not allow changing baudrate when uartclk is not available ALSA: firewire-lib: Fix 'amdtp_domain_start()' when no AMDTP_OUT_STREAM stream is found powerpc/papr_scm: Make 'perf_stats' invisible if perf-stats unavailable powerpc/64s: Fix copy-paste data exposure into newly created tasks powerpc/papr_scm: Properly handle UUID types and API powerpc: Offline CPU in stop_this_cpu() serial: 8250: 8250_omap: Fix possible interrupt storm on K3 SoCs serial: 8250: 8250_omap: Disable RX interrupt after DMA enable selftests/ftrace: fix event-no-pid on 1-core machine leds: ktd2692: Fix an error handling path leds: as3645a: Fix error return code in as3645a_parse_node() ASoC: fsl_spdif: Fix unexpected interrupt after suspend ASoC: Intel: sof_sdw: add SOF_RT715_DAI_ID_FIX for AlderLake configfs: fix memleak in configfs_release_bin_file ASoC: atmel-i2s: Fix usage of capture and playback at the same time powerpc/powernv: Fix
[Kernel-packages] [Bug 1937010] Re: Focal update: v5.10.47 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1937010 Title: Focal update: v5.10.47 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.10.47 upstream stable release from git://git.kernel.org/ Linux 5.10.47 integrity: Load mokx variables into the blacklist keyring certs: Add ability to preload revocation certs certs: Move load_system_certificate_list to a common function certs: Add EFI_CERT_X509_GUID support for dbx entries Revert "drm: add a locked version of drm_is_current_master" netfs: fix test for whether we can skip read when writing beyond EOF swiotlb: manipulate orig_addr when tlb_addr has offset KVM: SVM: Call SEV Guest Decommission if ASID binding fails mm, futex: fix shared futex pgoff on shmem huge page mm/thp: another PVMW_SYNC fix in page_vma_mapped_walk() mm/thp: fix page_vma_mapped_walk() if THP mapped by ptes mm: page_vma_mapped_walk(): get vma_address_end() earlier mm: page_vma_mapped_walk(): use goto instead of while (1) mm: page_vma_mapped_walk(): add a level of indentation mm: page_vma_mapped_walk(): crossing page table boundary mm: page_vma_mapped_walk(): prettify PVMW_MIGRATION block mm: page_vma_mapped_walk(): use pmde for *pvmw->pmd mm: page_vma_mapped_walk(): settle PageHuge on entry mm: page_vma_mapped_walk(): use page for pvmw->page mm: thp: replace DEBUG_VM BUG with VM_WARN when unmap fails for split mm/thp: unmap_mapping_page() to fix THP truncate_cleanup_page() mm/thp: fix page_address_in_vma() on file THP tails mm/thp: fix vma_address() if virtual address below file offset mm/thp: try_to_unmap() use TTU_SYNC for safe splitting mm/thp: make is_huge_zero_pmd() safe and quicker mm/thp: fix __split_huge_pmd_locked() on shmem migration entry mm, thp: use head page in __migration_entry_wait() mm/rmap: use page_not_mapped in try_to_unmap() mm/rmap: remove unneeded semicolon in page_not_mapped() mm: add VM_WARN_ON_ONCE_PAGE() macro x86/fpu: Make init_fpstate correct with optimized XSAVE x86/fpu: Preserve supervisor states in sanitize_restored_user_xstate() kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync() kthread_worker: split code for canceling the delayed work timer ceph: must hold snap_rwsem when filling inode for async create i2c: robotfuzz-osif: fix control-request directions KVM: do not allow mapping valid but non-reference-counted pages s390/stack: fix possible register corruption with stack switch helper nilfs2: fix memory leak in nilfs_sysfs_delete_device_group scsi: sd: Call sd_revalidate_disk() for ioctl(BLKRRPART) gpiolib: cdev: zero padding during conversion to gpioline_info_changed i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access pinctrl: stm32: fix the reported number of GPIO lines per bank perf/x86: Track pmu in per-CPU cpu_hw_events net: ll_temac: Avoid ndo_start_xmit returning NETDEV_TX_BUSY net: ll_temac: Add memory-barriers for TX BD access PCI: Add AMD RS690 quirk to enable 64-bit DMA recordmcount: Correct st_shndx handling mac80211: handle various extensible elements correctly mac80211: reset profile_periodicity/ema_ap net: qed: Fix memcpy() overflow of qed_dcbx_params() KVM: selftests: Fix kvm_check_cap() assertion r8169: Avoid memcpy() over-reading of ETH_SS_STATS sh_eth: Avoid memcpy() over-reading of ETH_SS_STATS r8152: Avoid memcpy() over-reading of ETH_SS_STATS net/packet: annotate accesses to po->ifindex net/packet: annotate accesses to po->bind net:
[Kernel-packages] [Bug 1938032] Re: Focal update: 5.10.52 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938032 Title: Focal update: 5.10.52 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.10.52 upstream stable release from git://git.kernel.org/ Linux 5.10.52 seq_file: disallow extremely large seq buffer allocations scsi: scsi_dh_alua: Fix signedness bug in alua_rtpg() MIPS: vdso: Invalid GIC access through VDSO mips: disable branch profiling in boot/decompress.o mips: always link byteswap helpers into decompressor static_call: Fix static_call_text_reserved() vs __init jump_label: Fix jump_label_text_reserved() vs __init sched/uclamp: Ignore max aggregation if rq is idle scsi: be2iscsi: Fix an error handling path in beiscsi_dev_probe() arm64: dts: rockchip: Re-add regulator-always-on for vcc_sdio for rk3399-roc-pc arm64: dts: rockchip: Re-add regulator-boot-on, regulator-always-on for vdd_gpu on rk3399-roc-pc firmware: turris-mox-rwtm: show message about HWRNG registration firmware: turris-mox-rwtm: fail probing when firmware does not support hwrng firmware: turris-mox-rwtm: report failures better firmware: turris-mox-rwtm: fix reply status decoding function thermal/drivers/rcar_gen3_thermal: Fix coefficient calculations ARM: dts: imx6q-dhcom: Add gpios pinctrl for i2c bus recovery ARM: dts: imx6q-dhcom: Fix ethernet plugin detection problems ARM: dts: imx6q-dhcom: Fix ethernet reset time properties thermal/drivers/sprd: Add missing MODULE_DEVICE_TABLE ARM: dts: am437x: align ti,pindir-d0-out-d1-in property with dt-shema ARM: dts: am335x: align ti,pindir-d0-out-d1-in property with dt-shema ARM: dts: dra7: Fix duplicate USB4 target module node arm64: dts: allwinner: a64-sopine-baseboard: change RGMII mode to TXID memory: fsl_ifc: fix leak of private memory on probe failure memory: fsl_ifc: fix leak of IO mapping on probe failure arm64: dts: ti: k3-j721e-main: Fix external refclk input to SERDES arm64: dts: renesas: r8a779a0: Drop power-domains property from GIC node reset: bail if try_module_get() fails ARM: dts: BCM5301X: Fixup SPI binding dt-bindings: i2c: at91: fix example for scl-gpios firmware: arm_scmi: Reset Rx buffer to max size during async commands firmware: tegra: Fix error return code in tegra210_bpmp_init() arm64: dts: qcom: trogdor: Add no-hpd to DSI bridge node ARM: dts: stm32: Rework LAN8710Ai PHY reset on DHCOM SoM ARM: dts: stm32: Connect PHY IRQ line on DH STM32MP1 SoM arm64: dts: renesas: r8a7796[01]: Fix OPP table entry voltages arm64: dts: renesas: Add missing opp-suspend properties arm64: dts: ti: j7200-main: Enable USB2 PHY RX sensitivity workaround ARM: dts: r8a7779, marzen: Fix DU clock names arm64: dts: renesas: v3msk: Fix memory size rtc: fix snprintf() checking in is_rtc_hctosys() ARM: dts: sun8i: h3: orangepi-plus: Fix ethernet phy-mode memory: pl353: Fix error return code in pl353_smc_probe() reset: brcmstb: Add missing MODULE_DEVICE_TABLE memory: atmel-ebi: add missing of_node_put for loop iteration memory: stm32-fmc2-ebi: add missing of_node_put for loop iteration ARM: dts: exynos: fix PWM LED max brightness on Odroid XU4 ARM: dts: exynos: fix PWM LED max brightness on Odroid HC1 ARM: dts: exynos: fix PWM LED max brightness on Odroid XU/XU3 ARM: exynos: add missing of_node_put for loop iteration reset: a10sr: add missing of_match_table reference reset: RESET_INTEL_GW should depend on X86 reset: RESET_BRCMSTB_RESCAL should depend on ARCH_BRCMSTB ARM: dts: gemini-rut1xx: remove duplicate ethernet node hexagon:
[Kernel-packages] [Bug 1938025] Re: Focal update: 5.10.48 upstream stable release
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-41073 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938025 Title: Focal update: 5.10.48 upstream stable release Status in linux-oem-5.10 package in Ubuntu: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.10.48 upstream stable release from git://git.kernel.org/ Linux 5.10.48 Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" RDMA/mlx5: Block FDB rules when not in switchdev mode gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP drm/nouveau: fix dma_address check for CPU/GPU sync gpio: mxc: Fix disabled interrupt wake-up support scsi: sr: Return appropriate error code when disk is ejected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1938025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1049.51 --- linux-oem-5.10 (5.10.0-1049.51) focal; urgency=medium * focal/linux-oem-5.10: 5.10.0-1049.50 -proposed tracker (LP: #1944209) * e1000e extremly slow (LP: #1930754) - SAUCE: e1000e: Separate TGP board type from SPT - SAUCE: e1000e: Fixing packet loss issues on new platforms * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() -- Chia-Lin Kao (AceLan) Mon, 27 Sep 2021 18:33:36 +0800 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944382] Re: Enable runtime power management for yellow carp XHCI
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1005.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1944382 Title: Enable runtime power management for yellow carp XHCI Status in amd: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: Alex Hung 7:01 PM (1 minute ago) to kernel-team BugLink: https://bugs.launchpad.net/bugs/1944382 [Impact] XHCI controllers of yellow carp by default will not use runtime PM [Fix] Add PCI Device IDs to enable runtime PM The patch can be found @ https://patchwork.kernel.org/project/linux- usb/patch/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/ [Test] This is requested and tested by AMD as described in LP:1944382 [Where problems could occur] Low risk. This only affects devices of AMD's Yellow Carp. == original descriptions == Like all XHCI controllers yellow carp XHCI by default will not use runtime PM and needs to be added to an allow list. AMD has validated that XHCI runtime PM is safe. Please include https://lore.kernel.org/linux- usb/20210920154100.3195683-1-nehal-bakulchandra.s...@amd.com/T/#u in OEM-5.14 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1944382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945438] Re: Update ADL-P dmc firmware
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1005.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945438 Title: Update ADL-P dmc firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works without issues. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945556] Re: Fix missing HDMI audio on Intel RKL
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1005.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945556 Title: Fix missing HDMI audio on Intel RKL Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] HDMI audio is missing on Intel RKL. [Fix] Also use BIOS provided value for HDA link. [Test] HDMI audio is back after the fix gets applied. [Where problems could occur] Because this is a regression, this patch simply brings back the old behavior for RKL systems. There could be RKL systems get fixed by the offending commit, so this might break those hypothetical systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] 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 1945967 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Incomplete Bug description: 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) 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 1879328] Re: ubuntu_kvm_unit_test failed to build on Focal PowerPC
Test can be built on Focal PowerPC now. (Cannot be built on H-ppc, see bug 1931534) ** Changed in: ubuntu-kernel-tests Status: In Progress => 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/1879328 Title: ubuntu_kvm_unit_test failed to build on Focal PowerPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Compilation failed with: ld: ld: powerpc/selftest.elfpowerpc/spapr_hcall.elf: error: PHDR segment not covered by LOAD segment: error: PHDR segment not covered by LOAD segment ld: powerpc/rtas.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/emulator.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/sprs.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/tm.elf: error: PHDR segment not covered by LOAD segment Full build log: $ sudo make -j156 standalone gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.selftest.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/selftest.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/selftest.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.spapr_hcall.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/spapr_hcall.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/spapr_hcall.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.rtas.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/rtas.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/rtas.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.emulator.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/emulator.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/emulator.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.tm.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/tm.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/tm.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
Looks like Debian already fixed it. And their patch names are different :P -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Triaged Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.8 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-hwe-5.8 source package in Xenial: Invalid Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-hwe-5.8 source package in Bionic: Invalid Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-azure-5.8 source package in Focal: New Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure-5.8 source package in Hirsute: Invalid Status in linux-hwe-5.8 source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. * $ sudo ls /sys/firmware/efi/mok-variables MokListRT MokListXRT SbatLevelRT When booted with shim, the mok-variables directory above should exist, and contain at least `MokListRT MokListXRT SbatLevelRT` files. In kernel messages, the CA certificate should be loaded via MOKvar table i.e: * $ sudo journalctl -b -k | grep -A1 'MOKvar table' Sep 27 13:11:04 champion-spaniel kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Sep 27 13:11:04 champion-spaniel kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted
[Kernel-packages] [Bug 1945967] [NEW] rtw89 kernel module for Realtek 8852 wifi is missing
Public bug reported: 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) ** 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/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: New Bug description: 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) 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 1930754] Re: e1000e extremly slow
With cubic I have generated a new ISO with kernel 5.10.0-1049.51 installed. 1) PXE boot is working as fast as it should be. 2) Once O.S. installed download speeds are working as expected again. So I can confirm this patch fixes the issue When will this patch be included in the 5.11 generic kernel? -- 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/1930754 Title: e1000e extremly slow Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress 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: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress 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: [Impact] e1000e on TGP PCH encounters a network speed issue that rx speed is below 1MB/s [Fix] Intel provides 2 patches to fix this https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=263466 [Test] Verified by our Dell and Lenovo platforms and the bug reporter. [Where problems could occur] The fix only applies to e1000e with TGP PCH, and add a flag "E1000_FFLT_DBG_DONT_GATE_WAKE_DMA_CLK". The impact should be minimized and should not lead to other regressions. = We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
Well we have no evidence of which process or component is crashing or freezing so anything is possible at this stage. ** Summary changed: - [nvidia] Xorg freeze + [nvidia] System freeze -- 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/1945749 Title: [nvidia] System freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
My previous laptop (Dell Precision 5530, Ubuntu 20.04) was using the Nouveau display drivers If I remember correctly before switching to Dell Precision 5550 and I had same sort of crashes. If this bug is really related to graphics driver, which I'm not so sure at this point to be honest, I suspect that it will also happen when I switch to 460. I will switch to 460 just to be sure. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)
The relevant part of the kern.log is already within the description. As the server is in production we needed to return to previous kernel. ** 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/1945868 Title: focal kvm virtio_net set_features failed (-22) Status in linux package in Ubuntu: Confirmed Status in qemu-kvm package in Ubuntu: New Bug description: Setup linux-modules-5.4.0-88-generic within focal guest on a (equal) ubuntu 20.04 kvm bare metal machine. When using virtio as network driver it is failing with: net eth0: Fail to set guest offload. virtio_net virtio1 eth0: set_features() failed (-22); wanted 0x008000174a29, left 0x0 0800017ca29 followed by further kern log entries: [ cut here ] netdevice: br0: failed to disable 0x8000 on eth0! WARNING: CPU: 0 PID: 1048 at net/core/dev.c:8683 __netdev_update_features+0x4d1/0x9f0 Modules linked in: macvlan virtio_gpu ttm drm_kms_helper fb_sys_fops input_leds syscopyarea joydev sysfillrect serio_raw sysimgblt mac_hid sch_fq_codel 9p fscache 9pnet_virtio 9pnet bridge stp llc drm virtio_rng ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c psmouse virtio_net i2c_piix4 virtio_blk net_failover failover pata_acpi floppy CPU: 0 PID: 1048 Comm: brctl Tainted: GW 5.4.0-88-generic #99-Ubuntu Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 RIP: 0010:__netdev_update_features+0x4d1/0x9f0 Code: c7 c2 9b 30 9b a0 4c 8b 4d 88 48 85 c0 4d 0f 44 d4 4d 89 f0 48 8d 4d b8 4c 89 ca 4c 89 d6 48 c7 c7 d0 94 a3 a0 e8 dc 2d 19 00 <0f> 0b e9 5b fe ff ff 8b 45 9c 85 c0 0f 84 96 00 00 00 8b 45 9c f7 RSP: 0018:bf1840e0ba98 EFLAGS: 00010282 RAX: RBX: 000f RCX: 0006 RDX: 0007 RSI: 0082 RDI: 9c2c13a178c0 RBP: bf1840e0bb10 R08: 02d1 R09: 0004 R10: R11: 0001 R12: 9c2c0b258000 R13: 9c2c0b2580c0 R14: 9c2c0615a000 R15: 000f FS: 7f98be558580() GS:9c2c13a0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fffc24a1080 CR3: 00030b3e4000 CR4: 06f0 Call Trace: netdev_update_features+0x25/0x60 br_device_event+0x20f/0x300 [bridge] notifier_call_chain+0x55/0x80 raw_notifier_call_chain+0x16/0x20 call_netdevice_notifiers_info+0x2e/0x60 netdev_update_features+0x59/0x60 dev_disable_lro+0x21/0xf0 br_add_if+0x301/0x650 [bridge] add_del_if+0x67/0x80 [bridge] br_dev_ioctl+0x54/0x80 [bridge] dev_ifsioc+0xe5/0x3e0 ? _cond_resched+0x19/0x30 dev_ioctl+0x2dd/0x470 sock_do_ioctl+0xa8/0x140 ? evict+0x14c/0x1b0 sock_ioctl+0x24f/0x3c0 ? _cond_resched+0x19/0x30 ? get_max_files+0x20/0x20 do_vfs_ioctl+0x407/0x670 ksys_ioctl+0x67/0x90 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f98be47c50b Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48 RSP: 002b:7ffd783321e8 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 0002 RCX: 7f98be47c50b RDX: 7ffd78332210 RSI: 89a2 RDI: 0003 RBP: 7ffd78332210 R08: 0020 R09: fefefeff77686d74 R10: 7ffd78333e80 R11: 0246 R12: 7ffd78333e7e R13: 7ffd78333e7e R14: R15: ---[ end trace 240d361752e8f3f0 ]--- [ cut here ] Temporary solution is to return to the old rtl8139 driver and slow network down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
Unfortunately none of those crashes are related to the display. Since all the evidence we have so far is that this is some silent graphics freeze, I would recommend trying to uninstall the Nvidia 470 driver and install 460 instead, in the 'Additional Drivers' app. -- 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/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] Xorg freeze
Hi Daniel, https://errors.ubuntu.com/oops/b0a77a90-23bd-11ec-b3fd-fa163e6cac46 https://errors.ubuntu.com/oops/fff3b31a-2023-11ec-b459-fa163ee63de6 https://errors.ubuntu.com/oops/9d40eec4-1d63-11ec-b3e2-fa163ee63de6 https://errors.ubuntu.com/oops/ba6ac63a-1211-11ec-b21c-fa163ee63de6 https://errors.ubuntu.com/oops/f746ff84-1094-11ec-b1eb-fa163ee63de6 https://errors.ubuntu.com/oops/520722ce-0734-11ec-ae9b-fa163e6cac46 These are the error reports sent from my system. If there is anything else I can do, I'm all ears. -- 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/1945749 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945805] Re: Screen Won't Come Back After Blank Screen
*** This bug is a duplicate of bug 1944397 *** https://bugs.launchpad.net/bugs/1944397 It appears the vc4 kernel driver (Broadcom GPU) is crashing a lot in HDMI functions. We should treat this as a duplicate of bug 1944397 until proven otherwise. ** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu) ** This bug has been marked a duplicate of bug 1944397 HDMI does not display anything with Impish RPi desktop image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1945805 Title: Screen Won't Come Back After Blank Screen Status in linux-raspi package in Ubuntu: New Bug description: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-08-11 (50 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: Confirmed => Triaged -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Triaged Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945805] [NEW] Screen Won't Come Back After Blank Screen
You have been subscribed to a public bug: The Power Saving option was set for the screen to go blank after five minutes. After the update, the screen will now not come back on when the mouse or keyboard is utilized. The computer appears to be still operational as it's registering keystrokes, but it must be restarted in order for the screen to come back up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1019.20-raspi 5.11.22 Uname: Linux 5.11.0-1019-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:22:59 2021 DistUpgraded: 2021-08-11 11:39:13,437 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 003: ID 0424:2504 Microchip Technology, Inc. (formerly SMSC) Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1680x1050M@60 video=HDMI-A-2:1680x1050M@60 smsc95xx.macaddr=DC:A6:32:B4:5C:3E vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-08-11 (50 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session -- Screen Won't Come Back After Blank Screen https://bugs.launchpad.net/bugs/1945805 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Confirmed Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
Yes the bug seems to exist on impish in: /usr/share/dbus-1/services/org.bluez.obex.service Looks like it might originate from this 2013 patch: patches/0001-Allow-using-obexd-without-systemd-in-the-user- sessio.patch Perhaps it is meant to be @pkglibexecdir@ ? -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Confirmed Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945938] Re: [impish] Remove the downstream xr-usb-uart driver
** Description changed: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. + + [This is a tracking bug, please do not triage] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945938 Title: [impish] Remove the downstream xr-usb-uart driver Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: [Impact] The xr-usb-serial custom (downstream vendor) driver was added in Xenial LTS kernel to add support for USB UART chips: Family: USB UART Part Numbers: XR21V1410, XR21V1412, XR21V1414, XR21B1411, XR21B1420, XR21B1422, XR21B1424, XR22801, XR22802, XR22804 [Fix] In 5.13.x, support for these devices was added to the kernel via. following patch series: Link: https://lore.kernel.org/all/20210412095557.1213-1-jo...@kernel.org/ There have been long term maintenance challenges with the downstream vendor driver over the period of time (since 4.4.y based Xenial LTS). Now that upstream driver supports most of the above part numbers, let's remove this redundant out-of-tree driver. [Test] The driver was functionally verified to work fine with XR21V1412. The support for other chips with part numbers mentioned above are also supported with the above patch series. [Where problems could occur] The downstream driver was designed to work with specific BIOS configs only defined on an IoT GW project which is locked to use only Xenial ESM and Bionic LTS kernels, there is a low chance of regression on the Impish series. [This is a tracking bug, please do not triage] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
