[Kernel-packages] [Bug 2038507] [NEW] ucsi_acpi_async_write NULL pointer dereference on VivoBook_ASUSLaptop
Public bug reported: On my VivoBook laptop, I encountered a critical kernel error that caused a system crash. This error occurred while the system was running the 6.2.0-32-generic until 6.2.0-34-generic versions of the Ubuntu kernel, 6.2.0-31 works fine. The hardware used is an ASUS VivoBook K3502ZA with BIOS version K3502ZA.307, last updated on 09/08/2022. Detaching all USB devices does not fix the issue. Steps to Reproduce: Boot the VivoBook laptop. Start kernel Expected Behavior: The system should operate without encountering kernel NULL pointer dereference errors and subsequent crashes. Actual Behavior: The system crashes with the mentioned kernel error. Please let me know if you need further information or logs to investigate and resolve this bug. See: https://bugzilla.kernel.org/show_bug.cgi?id=217929 $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy linux-image-6.2.0-34-generic linux-image-6.2.0-34-generic: Installed: 6.2.0-34.34 Candidate: 6.2.0-34.34 Version table: *** 6.2.0-34.34 500 500 http://it.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-34 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasco 1271 F pipewire vasco 1272 F wireplumber /dev/snd/controlC1: vasco 1272 F wireplumber /dev/snd/seq:vasco 1271 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Oct 5 08:57:33 2023 InstallationDate: Installed on 2023-05-23 (135 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3502ZA_K3502ZA PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgkubuntu-root ro quiet splash nmi_watchdog=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: K3502ZA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K3502ZA 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: 208.32 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrK3502ZA.307:bd09/08/2022:br5.25:efr208.32:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopK3502ZA_K3502ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK3502ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: VivoBook_ASUSLaptop K3502ZA_K3502ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038507 Title: ucsi_acpi_async_write NULL pointer dereference on VivoBook_ASUSLaptop Status in linux package in Ubuntu: New Bug description: On my VivoBook laptop, I encountered a critical kernel error that caused a system crash. This error occurred while the system was running the 6.2.0-32-generic until 6.2.0-34-generic versions of the Ubuntu kernel, 6.2.0-31 works fine. The hardware used is an ASUS VivoBook K3502ZA with BIOS version K3502ZA.307, last updated on 09/08/2022. Detaching all USB devices does not fix the issue. Steps to Reproduce: Boot the VivoBook laptop. Start kernel Expected Behavior: The system should operate without encountering kernel NULL pointer dereference errors and subsequent crashes. Actual Behavior: The system crashes with the mentioned kernel error. Please let me know if you need further information or logs to investigate and resolve this bug. See: https://bugzilla.kernel.org/show_bug.cgi?id=217929 $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy linux-image-6.2.0-34-generic linux-image-6.2.0-34-generic: Installed: 6.2.0-34.34 Candidate: 6.2.0-34.34 Version
[Kernel-packages] [Bug 2038508] [NEW] package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: xxx ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 3916 F wireplumber /dev/snd/controlC1: willem 3916 F wireplumber /dev/snd/seq:willem 3902 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 09:13:13 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (348 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2038508 Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: xxx ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 3916 F wireplumber /dev/snd/controlC1: willem 3916 F wireplumber /dev/snd/seq:willem 3902 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 09:13:13 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (348 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2038508/+subscriptions -- Mailing list: htt
[Kernel-packages] [Bug 2038507] 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/2038507 Title: ucsi_acpi_async_write NULL pointer dereference on VivoBook_ASUSLaptop Status in linux package in Ubuntu: Confirmed Bug description: On my VivoBook laptop, I encountered a critical kernel error that caused a system crash. This error occurred while the system was running the 6.2.0-32-generic until 6.2.0-34-generic versions of the Ubuntu kernel, 6.2.0-31 works fine. The hardware used is an ASUS VivoBook K3502ZA with BIOS version K3502ZA.307, last updated on 09/08/2022. Detaching all USB devices does not fix the issue. Steps to Reproduce: Boot the VivoBook laptop. Start kernel Expected Behavior: The system should operate without encountering kernel NULL pointer dereference errors and subsequent crashes. Actual Behavior: The system crashes with the mentioned kernel error. Please let me know if you need further information or logs to investigate and resolve this bug. See: https://bugzilla.kernel.org/show_bug.cgi?id=217929 $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy linux-image-6.2.0-34-generic linux-image-6.2.0-34-generic: Installed: 6.2.0-34.34 Candidate: 6.2.0-34.34 Version table: *** 6.2.0-34.34 500 500 http://it.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-34 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasco 1271 F pipewire vasco 1272 F wireplumber /dev/snd/controlC1: vasco 1272 F wireplumber /dev/snd/seq:vasco 1271 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Oct 5 08:57:33 2023 InstallationDate: Installed on 2023-05-23 (135 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop K3502ZA_K3502ZA PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgkubuntu-root ro quiet splash nmi_watchdog=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: K3502ZA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K3502ZA 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: 208.32 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrK3502ZA.307:bd09/08/2022:br5.25:efr208.32:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopK3502ZA_K3502ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK3502ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Vivobook dmi.product.name: VivoBook_ASUSLaptop K3502ZA_K3502ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038512] [NEW] [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
Public bug reported: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules-load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. ** 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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in linux package in Ubuntu: New Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025054] Re: snap-kernel-uc22 lacks atheros firmware
** Also affects: canonical-kernel-snaps 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/2025054 Title: snap-kernel-uc22 lacks atheros firmware Status in canonical-kernel-snaps: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Summary] The Atheros firmware files aren't available in the snap-kernel-uc22 snap, used in Ubuntu Core Desktop, so the Bluetooth module in Asus Zenbook UX21-e (and probably in a lot more devices) doesn't work. [Steps to reproduce] Boot, from a power-down state, a device with an Atheros-based Bluetooth module, into Ubuntu Core Desktop, open a root terminal and type bluetoothctl devices It returns the error 'No default controller available', because the Bluetooth module firmware wasn't loaded. Now, from a power-down state, boot into an Ubuntu live session (for example, from an USB pendrive), and when the desktop appears, reboot the computer (without powering it down) into Ubuntu Core Desktop and type again in a root terminal bluetoothctl devices This time there is no error, because the Bluetooth device firmware was already loaded in the Ubuntu live session. [Expected result] The call to `bluetoothctl devices` should not return any error. [Actual result] The call to `bluetoothctl devices` returns the 'No default controller available' error. [Failure rate] 3/3 [Stage] Patch available to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2025054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038512] 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 2038512 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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037398] Re: kexec enable to load/kdump zstd compressed zimg
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2037398 Title: kexec enable to load/kdump zstd compressed zimg Status in kdump-tools package in Ubuntu: Invalid Status in kexec-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Released Bug description: While testing the 6.5.0-6-generic proposed arm64 generic kernel I encountered issues being able to use kdump. After enabling -proposed and installing the -proposed 6.5.0-6 kernel and rebooting I encountered the following: `kdump-config show` shows `current state:Not ready to kdump` and looking at the status of the kdump-tools services I see `Cannot determine the file type of /var/lib/kdump/vmlinuz` Full output: ``` ubuntu@cloudimg:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.5.0-6-generic current state:Not ready to kdump kexec command: no kexec command recorded ubuntu@cloudimg:~$ sudo service kdump-tools status ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; preset: enabled) Active: active (exited) since Tue 2023-09-26 09:21:44 UTC; 5min ago Process: 515 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 515 (code=exited, status=0/SUCCESS) CPU: 4min 21.329s Sep 26 09:16:14 cloudimg systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... Sep 26 09:16:24 cloudimg kdump-tools[515]: Starting kdump-tools: Sep 26 09:16:24 cloudimg kdump-tools[537]: * Creating symlink /var/lib/kdump/vmlinuz Sep 26 09:16:32 cloudimg kdump-tools[580]: kdump-tools: Generating /var/lib/kdump/initrd.img-6.5.0-6-generic Sep 26 09:21:42 cloudimg kdump-tools[537]: * Creating symlink /var/lib/kdump/initrd.img Sep 26 09:21:43 cloudimg kdump-tools[5538]: Cannot determine the file type of /var/lib/kdump/vmlinuz Sep 26 09:21:44 cloudimg kdump-tools[537]: * failed to load kdump kernel Sep 26 09:21:44 cloudimg kdump-tools[5539]: failed to load kdump kernel Sep 26 09:21:44 cloudimg systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. ubuntu@cloudimg:~$ ls -al /var/lib/kdump/vmlinuz lrwxrwxrwx 1 root root 29 Sep 26 09:16 /var/lib/kdump/vmlinuz -> /boot/vmlinuz-6.5.0-6-generic ubuntu@cloudimg:~$ file /var/lib/kdump/vmlinuz /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.5.0-6-generic ubuntu@cloudimg:~$ sudo file /boot/vmlinuz-6.5.0-6-generic /boot/vmlinuz-6.5.0-6-generic: PE32+ executable (EFI application) Aarch64 (stripped to external PDB), for MS Windows, 2 sections ``` The reboot with 6.5.0-6 was successful and the reboot after linux-crashdump install was successful too. I used https://ubuntu.com/server/docs/kernel-crash-dump guide for installing linux-crashdump and attempting to trigger a dump. I used arm64 qcow cloud image from http://cloud- images.ubuntu.com/mantic/20230925/mantic-server-cloudimg-arm64.img to test the above emulated on amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2037398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-aws - 6.5.0-1007.7 --- linux-aws (6.5.0-1007.7) mantic; urgency=medium * mantic/linux-aws: 6.5.0-1007.7 -proposed tracker (LP: #2037624) * SEV_SNP failure to init (LP: #2037316) - x86/sev-es: Allow copy_from_kernel_nofault in earlier boot - x86/sev-es: Only set x86_virt_bits to correct value * Miscellaneous Ubuntu changes - [Config] update toolchain version in annotations [ Ubuntu: 6.5.0-7.7 ] * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations [ Ubuntu: 6.5.0-6.6 ] * mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595) * Mantic update: v6.5.3 upstream stable release (LP: #2035588) - drm/amd/display: ensure async flips are only accepted for fast updates - cpufreq: intel_pstate: set stale CPU frequency to minimum - tpm: Enable hwrng only for Pluton on AMD CPUs - Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN - Revert "fuse: in fuse_flush only wait if someone wants the return code" - Revert "f2fs: clean up w/ sbi->log_sectors_per_block" - Revert "PCI: tegra194: Enable support for 256 Byte payload" - Revert "net: macsec: preserve ingress frame ordering" - reiserfs: Check the return value from __getblk() - splice: always fsnotify_access(in), fsnotify_modify(out) on success - splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice - splice: fsnotify_access(in), fsnotify_modify(out) on success in tee - eventfd: prevent underflow for eventfd semaphores - fs: Fix error checking for d_hash_and_lookup() - iomap: Remove large folio handling in iomap_invalidate_folio() - tmpfs: verify {g,u}id mount options correctly - selftests/harness: Actually report SKIP for signal tests - vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing - ARM: ptrace: Restore syscall restart tracing - ARM: ptrace: Restore syscall skipping for tracers - btrfs: zoned: skip splitting and logical rewriting on pre-alloc write - erofs: release ztailpacking pclusters properly - locking/arch: Avoid variable shadowing in local_try_cmpxchg() - refscale: Fix uninitalized use of wait_queue_head_t - clocksource: Handle negative skews in "skew is too large" messages - powercap: arm_scmi: Remove recursion while parsing zones - OPP: Fix potential null ptr dereference in dev_pm_opp_get_required_pstate() - OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd() - selftests/resctrl: Add resctrl.h into build deps - selftests/resctrl: Don't leak buffer in fill_cache() - selftests/resctrl: Unmount resctrl FS if child fails to run benchmark - selftests/resctrl: Close perf value read fd on errors - sched/fair: remove util_est boosting - arm64/ptrace: Clean up error handling path in sve_set_common() - sched/psi: Select KERNFS as needed - cpuidle: teo: Update idle duration estimate when choosing shallower state - x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved - arm64/fpsimd: Only provide the length to cpufeature for xCR registers - sched/rt: Fix sysctl_sched_rr_timeslice intial value - perf/imx_ddr: don't enable counter0 if none of 4 counters are used - selftests/futex: Order calls to futex_lock_pi - irqchip/loongson-eiointc: Fix return value checking of eiointc_index - ACPI: x86: s2idle: Post-increment variables when getting constraints - ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table - thermal/of: Fix potential uninitialized value access - cpufreq: amd-pstate-ut: Remove module parameter access - cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver - tools/nolibc: arch-*.h: add missing space after ',' - tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0 - x86/efistub: Fix PCI ROM preservation in mixed mode - cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit() - cpufreq: tegra194: add online/offline hooks - cpufreq: tegra194: remove opp table in exit hook - selftests/bpf: Fix bpf_nf failure upon test rerun - libbpf: only reset sec_def handler when necessary - bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie - bpftool: Define a local bpf_perf_link to fix accessing its fields - bpftool: Use a local copy of BPF_LINK_TYPE_PERF_EVENT in pid_iter.bpf.c - bpftool: Use a local bpf_perf_event_value to fix accessing its fields - libbpf: Fix realloc API handling in zero-siz
[Kernel-packages] [Bug 2037316] Re: SEV_SNP failure to init
This bug was fixed in the package linux-gcp - 6.5.0-1006.6 --- linux-gcp (6.5.0-1006.6) mantic; urgency=medium * mantic/linux-gcp: 6.5.0-1006.6 -proposed tracker (LP: #2037626) * SEV_SNP failure to init (LP: #2037316) - x86/sev-es: Allow copy_from_kernel_nofault in earlier boot - x86/sev-es: Only set x86_virt_bits to correct value * Miscellaneous Ubuntu changes - [Config] update gcc version in annotations [ Ubuntu: 6.5.0-7.7 ] * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations [ Ubuntu: 6.5.0-6.6 ] * mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595) * Mantic update: v6.5.3 upstream stable release (LP: #2035588) - drm/amd/display: ensure async flips are only accepted for fast updates - cpufreq: intel_pstate: set stale CPU frequency to minimum - tpm: Enable hwrng only for Pluton on AMD CPUs - Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN - Revert "fuse: in fuse_flush only wait if someone wants the return code" - Revert "f2fs: clean up w/ sbi->log_sectors_per_block" - Revert "PCI: tegra194: Enable support for 256 Byte payload" - Revert "net: macsec: preserve ingress frame ordering" - reiserfs: Check the return value from __getblk() - splice: always fsnotify_access(in), fsnotify_modify(out) on success - splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice - splice: fsnotify_access(in), fsnotify_modify(out) on success in tee - eventfd: prevent underflow for eventfd semaphores - fs: Fix error checking for d_hash_and_lookup() - iomap: Remove large folio handling in iomap_invalidate_folio() - tmpfs: verify {g,u}id mount options correctly - selftests/harness: Actually report SKIP for signal tests - vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing - ARM: ptrace: Restore syscall restart tracing - ARM: ptrace: Restore syscall skipping for tracers - btrfs: zoned: skip splitting and logical rewriting on pre-alloc write - erofs: release ztailpacking pclusters properly - locking/arch: Avoid variable shadowing in local_try_cmpxchg() - refscale: Fix uninitalized use of wait_queue_head_t - clocksource: Handle negative skews in "skew is too large" messages - powercap: arm_scmi: Remove recursion while parsing zones - OPP: Fix potential null ptr dereference in dev_pm_opp_get_required_pstate() - OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd() - selftests/resctrl: Add resctrl.h into build deps - selftests/resctrl: Don't leak buffer in fill_cache() - selftests/resctrl: Unmount resctrl FS if child fails to run benchmark - selftests/resctrl: Close perf value read fd on errors - sched/fair: remove util_est boosting - arm64/ptrace: Clean up error handling path in sve_set_common() - sched/psi: Select KERNFS as needed - cpuidle: teo: Update idle duration estimate when choosing shallower state - x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved - arm64/fpsimd: Only provide the length to cpufeature for xCR registers - sched/rt: Fix sysctl_sched_rr_timeslice intial value - perf/imx_ddr: don't enable counter0 if none of 4 counters are used - selftests/futex: Order calls to futex_lock_pi - irqchip/loongson-eiointc: Fix return value checking of eiointc_index - ACPI: x86: s2idle: Post-increment variables when getting constraints - ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table - thermal/of: Fix potential uninitialized value access - cpufreq: amd-pstate-ut: Remove module parameter access - cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver - tools/nolibc: arch-*.h: add missing space after ',' - tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0 - x86/efistub: Fix PCI ROM preservation in mixed mode - cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit() - cpufreq: tegra194: add online/offline hooks - cpufreq: tegra194: remove opp table in exit hook - selftests/bpf: Fix bpf_nf failure upon test rerun - libbpf: only reset sec_def handler when necessary - bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie - bpftool: Define a local bpf_perf_link to fix accessing its fields - bpftool: Use a local copy of BPF_LINK_TYPE_PERF_EVENT in pid_iter.bpf.c - bpftool: Use a local bpf_perf_event_value to fix accessing its fields - libbpf: Fix realloc API handling in zero-sized edg
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online Status in cloud-images: New Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on amd64 host. The bug is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This but is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ 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: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ 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: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@list
[Kernel-packages] [Bug 2035588] Re: Mantic update: v6.5.3 upstream stable release
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035588 Title: Mantic update: v6.5.3 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: 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: v6.5.3 upstream stable release from git://git.kernel.org/ Linux 6.5.3 drm/amd/display: Block optimize on consecutive FAMS enables revert "memfd: improve userspace warnings for missing exec-related flags". memfd: improve userspace warnings for missing exec-related flags memfd: replace ratcheting feature from vm.memfd_noexec with hierarchy memfd: do not -EACCES old memfd_create() users with vm.memfd_noexec=2 selftests/memfd: sysctl: fix MEMFD_NOEXEC_SCOPE_NOEXEC_ENFORCED mm/memfd: sysctl: fix MEMFD_NOEXEC_SCOPE_NOEXEC_ENFORCED serial: sc16is7xx: fix regression with GPIO configuration serial: sc16is7xx: remove obsolete out_thread label Bluetooth: HCI: Introduce HCI_QUIRK_BROKEN_LE_CODED Bluetooth: msft: Extended monitor tracking by address filter media: ipu3-cio2: allow ipu_bridge to be a module again perf/x86/uncore: Correct the number of CHAs on EMR x86/build: Fix linker fill bytes quirk/incompatibility for ld.lld x86/sgx: Break up long non-preemptible delays in sgx_vepc_release() x86/smp: Don't send INIT to non-present and non-booted CPUs USB: core: Fix oversight in SuperSpeed initialization of: property: fw_devlink: Add a devlink for panel followers cpufreq: brcmstb-avs-cpufreq: Fix -Warray-bounds bug crypto: stm32 - fix MDMAT condition crypto: stm32 - fix loop iterating through scatterlist for DMA HID: logitech-hidpp: rework one more time the retries attempts s390/dasd: fix string length handling s390/ipl: add missing secure/has_secure file to ipl type 'unknown' s390/dcssblk: fix kernel crash with list_add corruption RISC-V: Add ptrace support for vectors iov_iter: Fix iov_iter_extract_pages() with zero-sized entries regulator: dt-bindings: qcom,rpm: fix pattern for children arm64: sdei: abort running SDEI handlers during crash pstore/ram: Check start of empty przs during init mmc: renesas_sdhi: register irqs before registering controller platform/chrome: chromeos_acpi: print hex string for ACPI_TYPE_BUFFER crypto: af_alg - Decrement struct key.usage in alg_set_by_key_serial() x86/MCE: Always save CS register on AMD Zen IF Poison errors fsverity: skip PKCS#7 parser when keyring is empty net: handle ARPHRD_PPP in dev_is_mac_header_xmit() X.509: if signature is unsupported skip validation r8169: fix ASPM-related issues on a number of systems with NIC version from RTL8168h x86/sev: Make enc_dec_hypercall() accept a size instead of npages dccp: Fix out of bounds access in DCCP error handler dlm: fix plock lookup when using multiple lockspaces bpf: Fix issue in verifying allow_ptr_leaks drm/amd/display: Add smu write msg id fail retry process misc: fastrpc: Pass proper scm arguments for static process init parisc: Fix /proc/cpuinfo output for lscpu procfs: block chmod on /proc/thread-self/comm block: don't add or resize partition on the disk with GENHD_FL_NO_PART block: fix pin count management when merging same-page segments Revert "PCI: Mark NVIDIA T4 GPUs to avoid bus reset" ntb: Fix calculation ntb_transport_tx_free_entry() ntb: Clean up tx tail index on link down ntb: Drop packets when qp link is down dt-bindings: PCI: qcom: Fix SDX65 compatible PCI/PM: Only read PCI_PM_CTRL register when available PCI: hv: Fix a crash in hv_pci_restore_msi_msg() during hibernation PCI: Free released resource after coalescing scsi: mpt3sas: Perform additional ret
[Kernel-packages] [Bug 2035583] Re: Mantic update: v6.5.2 upstream stable release
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035583 Title: Mantic update: v6.5.2 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: 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: v6.5.2 upstream stable release from git://git.kernel.org/ Linux 6.5.2 pinctrl: amd: Don't show `Invalid config param` errors usb: typec: tcpci: clear the fault status bit nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse tracing: Zero the pipe cpumask on alloc to avoid spurious -EBUSY dt-bindings: sc16is7xx: Add property to change GPIO function tcpm: Avoid soft reset when partner does not support get_status fsi: master-ast-cf: Add MODULE_FIRMWARE macro firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe serial: sc16is7xx: fix bug when first setting GPIO direction serial: sc16is7xx: fix broken port 0 uart init serial: qcom-geni: fix opp vote on shutdown wifi: ath11k: Cleanup mac80211 references on failure during tx_complete wifi: ath11k: Don't drop tx_status when peer cannot be found wifi: rtw88: usb: kill and free rx urbs on probe failure wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU wifi: mt76: mt7921: do not support one stream on secondary antenna only staging: rtl8712: fix race condition HID: wacom: remove the battery when the EKR is off usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 usb: dwc3: meson-g12a: do post init to fix broken usb after resumption ALSA: usb-audio: Fix init call orders for UAC1 USB: serial: option: add FOXCONN T99W368/T99W373 product USB: serial: option: add Quectel EM05G variant (0x030e) modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index mmc: au1xmmc: force non-modular build and remove symbol_get usage ARM: pxa: remove use of symbol_get() ksmbd: reduce descriptor size if remaining bytes is less than request size ksmbd: replace one-element array with flex-array member in struct smb2_ea_info ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob() ksmbd: fix wrong DataOffset validation of create context erofs: ensure that the post-EOF tails are all zeroed drm/amdgpu: correct vmhub index in GMC v10/11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035581] Re: Mantic update: v6.5.1 upstream stable release
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035581 Title: Mantic update: v6.5.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: 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: v6.5.1 upstream stable release from git://git.kernel.org/ ACPI: thermal: Drop nocrt parameter module: Expose module_init_layout_section() arm64: module: Use module_init_layout_section() to spot init sections ARM: module: Use module_init_layout_section() to spot init sections ipv6: remove hard coded limitation on ipv6_pinfo lockdep: fix static memory detection even more kallsyms: Fix kallsyms_selftest failure Linux 6.5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034506] Re: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) 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/2034506 Title: Audio device fails to function randomly on Intel MTL platform: No CPC match in the firmware file's manifest Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2034506 [Impact] Audio device fails to function randomly on Intel MTL platform: ``` sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA path sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID: 9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's manifest (ibs/obs: 384/192) ``` [Fix] Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF: ipc4-topology: Add module parameter to ignore the CPC value") that to allow ignoring CPC validation for current fw release. [Test Case] 1. Boot into OS 2. Check if the internal audio input & output devices work 3. Let system enter suspend, then wake system back up 4. Check if the audio input & output devices work 5. Connect an external audio device (e.g. bluetooth headset, external monitor) and check if they work 6. Disconnect the external audio device 7. Check if the internal audio input & output devices work 8. Reboot system 9. Repeat above steps [Where problems could occur] While a 0 CPC value will force the DSP to run at full speed, this is going to impact power consumption until further fix being released for firmware. [Other Info] CPC checking landed to v6.5-rc1, so Mantic and oem-6.5 are nominated for fix. == original bug report == sof-audio-pci-intel-mtl :00:1f.3: no llp found, fall back to default HDA path sof-audio-pci-intel-mtl :00:1f.3: COPIER (UUID: 9BA00C83-CA12-4A83-943C-1FA2E82F9DDA): No CPC match in the firmware file's manifest (ibs/obs: 384/192) Proposed fix in upstream commit 26ef47e5ba60 ("ASoC: SOF: ipc4-topology: Add module parameter to ignore the CPC value") that to allow ignoring CPC validation for current fw release. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Invalid => 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/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035306] Re: Include QCA WWAN 5G Qualcomm SDX62/DW5932e support
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) 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/2035306 Title: Include QCA WWAN 5G Qualcomm SDX62/DW5932e support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] DW5932e is the new 5G QCA WWAN module for Dell platforms, it won't work without the IDs in the table. [Fix] This commit adds the required IDs to the table 104a8c5dd943 ("bus: mhi: host: pci_generic: Add support for Dell DW5932e") [Test case] 1. connect to the 5G WWAN through the GUI 2. make sure the network is working [Where problems could occur] It adds 2 IDs to the table, won't impact existing systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2035306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034061] Re: Default module signing algo should be accelerated
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2034061 Title: Default module signing algo should be accelerated Status in linux package in Ubuntu: Fix Released Bug description: [ Impact ] * Slow secureboot due to unoptimized signature verification algo [ Test Plan ] * Check config enforcement: If CONFIG_MODULE_SIG_(ALG)=y, then CONFIG_CRYPTO_(ALG)* should be =y as well [ Where problems could occur ] * Very old hardware incapable of a given optimisation will not gain from having optimised algo built-in [ Other Info ] * Full details Default module signing algo should be accelerated Default crypto signing algorithm for kernel modules, all its accelerated versions, should be built-in. This is to allow secureboot of accelerated machines to boot as quickly as possible when verifying each module signature. For example: given CONFIG_MODULE_SIG_SHA512=y All of CONFIG_CRYPTO_SHA512policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}> CONFIG_CRYPTO_SHA512note<'module signing'> CONFIG_CRYPTO_SHA512_ARMpolicy<{'armhf': 'm'}> CONFIG_CRYPTO_SHA512_ARM64 policy<{'arm64': 'm'}> CONFIG_CRYPTO_SHA512_ARM64_CE policy<{'arm64': 'm'}> CONFIG_CRYPTO_SHA512_S390 policy<{'s390x': 'm'}> CONFIG_CRYPTO_SHA512_SSSE3 policy<{'amd64': 'm'}> Should be =y on secureboot platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2033455 Title: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2033455 [Impact] Missing BT IDs for support for Intel Discrete Misty Peak2/BE202. [Fix] Bluetooth: a. kernel driver: - https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t - Also depends on patches for Gale Peak(BE200) from bug 2028065. b. firmware (shared with Gale Peak, to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030525] Re: Installation support for SMARC RZ/G2L platform
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030525 Title: Installation support for SMARC RZ/G2L platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Fix Released Bug description: Dear Maintainer The Ubuntu installation on Renesas RZ/G2L platform board is failing due to the following configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n10339 The configuration CONFIG_RESET_RZG2L_USBPHY_CTRL=y is required to allow the installation on Renesas SMARC platform. Alternatively, the module "reset-rzg2l-usbphy-ctrl.ko" to be added in the inside installer initrd. This change is required on Lunar and Jammy versions as well. Please update once the changes merged to test them on Renesas SMARC RZ/G2L platform. Best Regards John To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029199] Re: NULL pointer dereference on CS35L41 HDA AMP
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2029199 Title: NULL pointer dereference on CS35L41 HDA AMP Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [Impact] NULL pointer dereference happens because the HDA driver is trying to use CS35L41 HDA AMP before its probe routine is fully realized. [Fix] Use device link to enforce proper probe order. Since the fixing commit is part of a patch series, pull in the entire series which has several other important fixes too. [Test] Use dmesg to see if there's error. With the fix applied, no more kernel splat can be found. Hence the system can perform suspend, reboot and shutdown normally. [Where problems could occur] Though the entire series isn't trivia, it's not a major overhaul either. The entire changeset is limited to CS35L41 AMP, so the scope of regression risk is constrained. One possible risk factor is that it may require newer DSP firmware, and we'll monitor it closely on such scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029390] Re: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029390 Title: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Secure Execution guests must use the EP11 API ordinal 6 to create (generate, unwrap, derive) secure keys which encodes a NULL PIN (no session) as a string of zero-bytes. Therefore, the pkey module must be updated to check whether the Linux system is running as a secure guest and if so modify secure key creating requests (key(pair) gen, unwrap) to use ordinal 6 API. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028937] Re: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028937 Title: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Add support to the pkey kernel module to generate keys of key type PKEY_TYPE_EP11_AES. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2028937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2028065 Title: Support for Intel Discrete Gale Peak2/BE200 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] Missing Intel Gale Peak WiFi/Bluetooth support. [Fix] WIFI: a. kernel driver : - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix crash") [v6.5-rc2] b. firmware (to be released): - iwlwifi-gl-b0-fm-b0-83.ucode - iwlwifi-gl-b0-fm-b0.pnvm Bluetooth: a. kernel driver: - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak") - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)") b. firmware (to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc [Test Case] To boot with patched kernel and prereleased firmware blob and check basic WiFi/Bluetooth functions. [Where problems could occur] New device. Expect incomplete functions and bugs. [Other Info] Targets 6.5 kernels, so only nominated for Mantic and oem-6.5. = original bug report == WIFI: a. kernel driver : - commit 12a89f0177092 ("wifi: iwlwifi: remove 'use_tfh' config to fix crash") [v6.5-rc2] b. firmware (to be released): - iwlwifi-gl-b0-fm-b0-83.ucode - iwlwifi-gl-b0-fm-b0.pnvm Bluetooth: a. kernel driver: - commit 8fd791afddca ("Bluetooth: btintel: Add support for Gale Peak") - commit 24921786074b ("Bluetooth: Add support for Gale Peak (8087:0036)") b. firmware (to be released): - intel/ibt-0191-0191.sfi - intel/ibt-0191-0191.ddc To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Make backlight module auto detect dell_uart_backlight
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008882 Title: Make backlight module auto detect dell_uart_backlight Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] There are acpi_video* sysfs backlight interface in the system which are not working. For Dell AIO platforms, we use dell_uart_backlight to control the display brightness. The old way to fix this is to unregister acpi backlight interfaces in the backlight driver, but it may lead to some issues and the unregister function has been removed since v6.1-rc1 77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()") [Fix] The new way to do this is to collect all the quirk and auto detection method in video_detect.c I added an audo detection for the Dell AIO platoform to the driver which should do the same thing as the old way. [Test] Verified on the Dell AIO platform and confirmed there is only on dell_uart_backlight in the sysfs, and no acpi_video* interface. [Where problems could occur] There should be no regression potential, it uses different way to do the same thing, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003674] Re: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003674 Title: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Enable KVM and QEMU for AP passthrough to Secure Execution guests. This includes setup, configuration and teardown of AP related resources. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu) Status: Triaged => 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/2002226 Title: Add support for kernels compiled with CONFIG_EFI_ZBOOT Status in grub2 package in Ubuntu: Fix Released Status in grub2-unsigned package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in grub2-unsigned source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in grub2 source package in Jammy: Invalid Status in grub2-unsigned source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in grub2 source package in Lunar: Invalid Status in grub2-unsigned source package in Lunar: Invalid Status in linux source package in Lunar: Invalid Bug description: [Impact] Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header. Our GRUB fails to boot such a kernel. We should eliminate the following check: grub-core/loader/efi/linux.c:75: if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE) return grub_error(GRUB_ERR_BAD_OS, "invalid magic number"); This will allow any EFI binary to be run using the linux command. [Test plan] * check that grub and EFI based ARM64 machines boot * check that MAAS deployment works [Where problems could occur] * Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using piboot, u-boot, abootimg likely one still wants to build Image.gz and have CONFIG_EFI_ZBOOT disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Check for changes relevant for security certifications
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released 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 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
** Attachment added: "lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+attachment/5707004/+files/lsmod-i1200-demo-kernel-6.2-dracut-initrd.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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
** Attachment added: "mediatek-drivers-for-mt8195-demo-bringup.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+attachment/5707005/+files/mediatek-drivers-for-mt8195-demo-bringup.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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035591] Re: [Mediatek] mt8195-demo: Fix regulator kernel setting are missing: causes peripheral probe failure for linux (include installer)
This issue can be closed. New issue is created. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038512 Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035591 Title: [Mediatek] mt8195-demo: Fix regulator kernel setting are missing: causes peripheral probe failure for linux (include installer) Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: New Status in linux source package in Mantic: Confirmed Bug description: [Impact] peripheral probe failure [Fix] Compare to generic kernel config for arm64 file: arch/arm64/configs/defconfig The following settings should be enabled "built-in" in generic kernel settings. CONFIG_REGULATOR_MT6357=y CONFIG_REGULATOR_MT6358=y CONFIG_REGULATOR_MT6359=y CONFIG_REGULATOR_MT6360=y CONFIG_REGULATOR_MT6397=y [Test] 1. u-boot: [2023-04-26 14:34:28.294] run distro_bootcmd 2. disable silent mode in grub menu [2023-04-26 14:34:42.196] GNU GRUB version 2.06 3. boot to Linux [2023-04-26 14:35:09.115] [ 0.00] Linux version 6.2.0-18-generic (buildd@bos02-arm64-039) (aarch64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #18-Ubuntu SMP PREEMPT_DYNAMIC Sun Mar 19 19:49:50 UTC 2023 (Ubuntu 6.2.0-18.18-generic 6.2.6) [2023-04-26 14:35:09.115] [ 0.00] Machine model: MediaTek MT8195 demo board 4. lots of error and driver probing deffered. USB, Ethernet, MMC and multimedia interfaces. Ex: [2023-04-26 14:35:22.624] [ 13.808645] platform 1c014000.merge0: deferred probe pending 5. No ethernet and U-disk could be found [2023-04-26 14:36:15.548] Unable to find a medium containing a live file system [2023-04-26 14:36:15.548] Attempt interactive netboot from a URL? [2023-04-26 14:36:15.548] yes no (default yes): no [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) [2023-04-26 14:36:21.432] Enter 'help' for a list of built-in commands. [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] (initramfs) Unable to find a medium containing a live file system [Where problems could occur] [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029390] Re: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029390 Title: [23.10 FEAT] [SEC2352] pkey: support EP11 API ordinal 6 for secure guests Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Secure Execution guests must use the EP11 API ordinal 6 to create (generate, unwrap, derive) secure keys which encodes a NULL PIN (no session) as a string of zero-bytes. Therefore, the pkey module must be updated to check whether the Linux system is running as a secure guest and if so modify secure key creating requests (key(pair) gen, unwrap) to use ordinal 6 API. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2029390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003674] Re: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003674 Title: [23.10 FEAT] KVM: Enable Secure Execution Crypto Passthrough - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Enable KVM and QEMU for AP passthrough to Secure Execution guests. This includes setup, configuration and teardown of AP related resources. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038522] [NEW] disable shiftfs
Public bug reported: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out-of- tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) 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/2038522 Title: disable shiftfs Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
libcamera is not shipped on the images, and will be SRUed once tested. ** Changed in: pipewire (Ubuntu) Status: Triaged => Invalid ** Changed in: libcamera (Ubuntu) Milestone: None => mantic-updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038522] 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 2038522 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/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Incomplete Status in linux source package in Mantic: Incomplete Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032959] Re: ceph: support idmapped mounts
JFYI. All that you need to properly backport this series is: 1. port https://github.com/torvalds/linux/commit/ce0d5bd3a6c176f9a3bf867624a07119dd4d0878 (as this patch changes cephfs network protocol and have to be applied before cephfs idmapped mounts as in this feature we are extending cephfs network protocol too) 2. apply patches from https://lore.kernel.org/all/20230807132626.182101-1-aleksandr.mikhalit...@canonical.com/ (alternatively you can take patches from https://github.com/ceph/ceph-client/commits/testing starting from commit https://github.com/ceph/ceph-client/commit/6efd3e9974a02bda26e039ce81a3824db3cee74f until https://github.com/ceph/ceph-client/commit/5a077938dadefa2b159267718d7998ca880aeb9c ) As I can see here https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/commit/fs/ceph?h=master- next&id=e5e9604b7311bda41ffe266dbd60cf1eb637611b you have also backported fscrypt series. It's not a strict requirement or dependency. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032959 Title: ceph: support idmapped mounts Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] Now that zfs supports idmapped mounts the only user of shiftfs remains ceph. However a patch set has been posted upstream to enable such feature also in ceph: https://lore.kernel.org/all/20230807132626.182101-1-aleksandr.mikhalit...@canonical.com/ This is also maintained in this github repository: https://github.com/ceph/ceph-client.git Include this patch in our mantic kernel, so that the LXD team can do some testing to see if we can get rid of shiftfs and rely completely on upstream idmapped mounts. [Test case] Create an LXD container using a ceph backend, disable shiftfs and verify if everything is still working (LXD team will provide a proper test case for this). [Fix] Apply idmapped mounts patch set from: https://github.com/ceph/ceph-client.git [Regression potential] This patch set is still not upstream and still experimental, therefore we may experience regression or system crashes in systems that are using the ceph filesystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032959/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038522] Re: disable shiftfs
** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038522 Title: disable shiftfs Status in linux package in Ubuntu: Triaged Status in linux source package in Mantic: Triaged Bug description: [Impact] Now that all the filesystems that we officially support have the idmapped mounts capability we can get rid of shiftfs. The benefit of this change is that we don't have to maintain an out- of-tree filesystem anymore and we can completely rely on upstream features. [Test case] lxd was the main user of shiftfs to compensate the lack of idmapped mounts capability of certain filesystems, such as zfs / ceph, but now in mantic also these two filesystem received the support for idmapped mounts (support for zfs was introduced in 2.2.0~rc3 and for ceph see LP: #2032959). The lxd team provided a positive feedback, testing the latest 6.5 Mantic kernel across all the supported filesystems with shiftfs disabled. [Fix] Disable shiftfs in the kernel config and enable unsafe idmapped mounts by default (default=on). [Regression potential] The support for idmapped mounts for the ceph filesystem is not applied upstream yet, so we may experience regressions in systems that are using this filesystem. Moreover disabling shiftfs may trigger failures in our testing (testing shiftfs capabilities will obviously fail) or break any other user-space application that is relying on shiftfs (however to our knowledge lxd was the only "official" user or shiftfs; for this reason we may also see potential regressions in lxd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038528] [NEW] testing bot states
Public bug reported: new bug ** 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/2038528 Title: testing bot states Status in linux package in Ubuntu: New Bug description: new bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
ubuntu kernel team does not handle which drivers do or do not get included in the initrd. Since this is stuff that affects generic, these should be added by default for modules=most mode by initramfs-tools. please contact ubuntu foundations team about this. ** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in initramfs-tools package in Ubuntu: New Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Kernel version] 6.2 [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025040] Re: increased power usage after upgrade from kinetic to lunar
6.2.0-34.34 has been released ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025040 Title: increased power usage after upgrade from kinetic to lunar Status in linux package in Ubuntu: Fix Released Bug description: Hi I have just upgrade and power usage is double or more under lunar. Kernel version went from 5.19.0-43 to 6.2.0-20. Running powertop, I see that C8 is being used with 5.19 but 6.2 does not go to a higher power saving state than C3. I tried the Ubuntu kernel from jammy ie 5.15.0-73. It also uses C8. I have also tried the 5.15.108 & 5.10.17 mainline kernels. Both of these do not go to higher power saving state than C3. All these tests have been run on the same partition ie. only the kernel version has changed. Laptop is a HP 15s-fq4011TU 11th Gen Intel with Tiger Lake Iris Xe graphics. So it seems to me: 1) Ubuntu has applied a patch to the mainline kernel that improves power saving in 5.15 and 5.19 2) This patch either hasn't been applied to 6.2 or no longer works. Could you pls let me know what other info you need or what I could look at next? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038531] [NEW] '-' has bad syntax: revision number is empty
Public bug reported: when install nvidia-340 this occurs ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038531 Title: '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Incomplete Bug description: when install nvidia-340 this occurs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038528] 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 2038528 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/2038528 Title: testing bot states Status in linux package in Ubuntu: Incomplete Bug description: new bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038531] 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 2038531 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/2038531 Title: '-' has bad syntax: revision number is empty Status in linux package in Ubuntu: Incomplete Bug description: when install nvidia-340 this occurs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028937] Re: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2028937 Title: [23.10 FEAT] [SEC2341] pkey: support generation of keys of type PKEY_TYPE_EP11_AES Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Add support to the pkey kernel module to generate keys of key type PKEY_TYPE_EP11_AES. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2028937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Ok in this case can you please open an upstream mesa bug? ** Changed in: mesa (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23
[Kernel-packages] [Bug 1930745] Re: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key
It has been reported to be a hardware issue - replacing keyboard helped: https://forums.lenovo.com/t5/ThinkPad-L-R-and-SL-series- Laptops/Keyboard-sometimes-act-as-if-it-s-stuck-and-stops- responding/m-p/5050395?page=1#5214941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1930745 Title: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.2 LTS on my ThinkPad L15 laptop. From time to time the keyboard gets stuck / locked up. Sometimes it takes days to happen, sometimes it happens within a few minutes. It also does not seem to depend on the programs I am running, it seems to be entirely random. Basically, I am working/playing on the laptop and then suddenly the key I pressed last "gets stuck" and the keyboard does not respond any more. Other than that everything is running fine and I can still use the mouse and so on, but logging out does not resolve the issue and only a restart seems to work. I have also tried connecting a USB keyboard while the problem is occurring. The external keyboard is then detected and works fine, the built-in keyboard stops sending the signal and remains unresponsive. I have already mentioned the problem here, but it could not be resolved: https://ubuntuforums.org/showthread.php?t=2460675 I have also contacted Lenovo Hardware Support, and ran their tests, but those did not return anything, so they said it was not a hardware issue. My best guess is that it is a bug in the driver for the AT Translated Set 2 keyboard (I have the German keyboard layout), which is listed as supported hardware. Current and latest driver version is 1.0.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 13:45:29 2021 InstallationDate: Installed on 2020-12-29 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 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.8/+bug/1930745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
@vorlon you did reverse-depends on the wrong package, -450 & -450-server are not the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035591] Re: [Mediatek] mt8195-demo: Fix regulator kernel setting are missing: causes peripheral probe failure for linux (include installer)
the regulators are built into the initrd by default. ** Changed in: linux (Ubuntu Lunar) Status: New => Incomplete ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => 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/2035591 Title: [Mediatek] mt8195-demo: Fix regulator kernel setting are missing: causes peripheral probe failure for linux (include installer) Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Bug description: [Impact] peripheral probe failure [Fix] Compare to generic kernel config for arm64 file: arch/arm64/configs/defconfig The following settings should be enabled "built-in" in generic kernel settings. CONFIG_REGULATOR_MT6357=y CONFIG_REGULATOR_MT6358=y CONFIG_REGULATOR_MT6359=y CONFIG_REGULATOR_MT6360=y CONFIG_REGULATOR_MT6397=y [Test] 1. u-boot: [2023-04-26 14:34:28.294] run distro_bootcmd 2. disable silent mode in grub menu [2023-04-26 14:34:42.196] GNU GRUB version 2.06 3. boot to Linux [2023-04-26 14:35:09.115] [ 0.00] Linux version 6.2.0-18-generic (buildd@bos02-arm64-039) (aarch64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #18-Ubuntu SMP PREEMPT_DYNAMIC Sun Mar 19 19:49:50 UTC 2023 (Ubuntu 6.2.0-18.18-generic 6.2.6) [2023-04-26 14:35:09.115] [ 0.00] Machine model: MediaTek MT8195 demo board 4. lots of error and driver probing deffered. USB, Ethernet, MMC and multimedia interfaces. Ex: [2023-04-26 14:35:22.624] [ 13.808645] platform 1c014000.merge0: deferred probe pending 5. No ethernet and U-disk could be found [2023-04-26 14:36:15.548] Unable to find a medium containing a live file system [2023-04-26 14:36:15.548] Attempt interactive netboot from a URL? [2023-04-26 14:36:15.548] yes no (default yes): no [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash) [2023-04-26 14:36:21.432] Enter 'help' for a list of built-in commands. [2023-04-26 14:36:21.432] [2023-04-26 14:36:21.432] (initramfs) Unable to find a medium containing a live file system [Where problems could occur] [Other info] effected kernel (5.19~latest) ubuntu kernel for lunar, Kinetic, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
I don't understand the comment about bumblebee as it has a tonne of alternatives: # apt show bumblebee-nvidia | grep Depends WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Depends: bumblebee (= 3.2.1-29), nvidia-driver-binary | nvidia- driver-525 | nvidia-driver-525-server | nvidia-driver-515 | nvidia- driver-515-server | nvidia-driver-510 | nvidia-driver-510-server | nvidia-driver-470 | nvidia-driver-470-server | nvidia-driver-450-server | nvidia-driver-418-server | nvidia-driver-390 You want that list to be updated? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037403] Re: PCI BARs larger than 128GB are disabled
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2037403 Title: PCI BARs larger than 128GB are disabled Status in linux package in Ubuntu: Incomplete Status in linux-bluefield package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] Current linux-bluefield kernel reports that PCI BARs larger than 128GB are disabled. Increase the maximum PCI BAR size from 128GB to 8TB for future expansion. [Test Plan] Use updated kernel with PCI device with PCI BARs larger than 128GB. [Where problems could occur] No potential problems are expected. [Other Info] Testing has been provided by the customer. This patch is a cherry-pick from the upstream 5.18 kernel. It is intended for linux-bluefield kernel re-spin but it may be also suitable for the generic kernel (separate submission). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
There are partial NBS remains of 440-server in the archive that must be removed. ** Changed in: bumblebee (Ubuntu) Status: New => In Progress ** Also affects: nvidia-graphics-drivers-440-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035163] Re: Avoid address overwrite in kernel_connect
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2035163 Title: Avoid address overwrite in kernel_connect Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Released Status in linux-gcp source package in Mantic: Fix Released Bug description: This fix is requested to resolve an issue with NFS-backed mounts when used with BPF-load-balancing: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=0bdf399342c5 Testing: - GCP has confirmed the fix works before proposing it upstream. I have verified basic network sanity with fix applied. Regression potenial: - The fix modifies kernel_connect() which can have an effect on all kinds of network connections. The change itself is very minor though and simply converts a pass-by-reference to a pass-by-value - so the risk is considered minimal. More information at: https://canonical.lightning.force.com/lightning/r/Case/5008e0HNldDAAT/view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035166] Re: NULL Pointer Dereference During KVM MMU Page Invalidation
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035166 Title: NULL Pointer Dereference During KVM MMU Page Invalidation Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] During VM live migration, there is a potential risk of dereferencing a NULL pointer, which can lead to memory access issues and result in an unstable environment. [Fix] The call trace is as follows: kernel: BUG: kernel NULL pointer dereference, address: 0008 kernel: #PF: supervisor write access in kernel mode kernel: #PF: error_code(0x0002) - not-present page kernel: PGD 0 P4D 0 kernel: Oops: 0002 [#1] SMP NOPTI kernel: CPU: 29 PID: 4063601 Comm: CPU 0/KVM Tainted: G IOE 5.15.0-53-generic #59~20.04.1-Ubuntu kernel: Hardware name: Dell Inc. PowerEdge R640/0H28RR, BIOS 2.12.2 07/09/2021 kernel: RIP: 0010:__handle_changed_spte+0x3a9/0x620 [kvm] kernel: Code: 48 8b 58 28 44 0f b6 63 24 48 8b 43 28 41 83 e4 0f 48 89 45 a0 0f 1f 44 00 00 45 84 d2 0f 85 06 02 00 00 48 8b 43 08 48 8b 13 <48> 89 42 08 48 89 10 44 0f b6 6b 23 48 b8 00 01 00 00 00 00 ad de kernel: RSP: 0018:b580320278a8 EFLAGS: 00010246 kernel: RAX: RBX: a0fe29e94c38 RCX: 0027 kernel: RDX: RSI: 0004 RDI: b5801e24ba58 kernel: RBP: b58032027930 R08: R09: 0004 kernel: R10: 0001 R11: R12: 0003 kernel: R13: 0004 R14: R15: b5801e235000 kernel: FS: 7f1553fff700() GS:a20eff78() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 0008 CR3: 00e7f7544004 CR4: 007726e0 kernel: PKRU: 5554 kernel: Call Trace: kernel: kernel: ? __switch_to_xtra+0x109/0x510 kernel: zap_gfn_range+0x218/0x360 [kvm] kernel: ? __smp_call_single_queue+0x59/0x90 kernel: ? alloc_cpumask_var_node+0x1/0x30 kernel: ? kvm_make_vcpus_request_mask+0x150/0x1d0 [kvm] kernel: kvm_tdp_mmu_zap_invalidated_roots+0x5b/0xb0 [kvm] kernel: kvm_mmu_zap_all_fast+0x19a/0x1d0 [kvm] -- kernel: RAX: ffda RBX: 4020ae46 RCX: 7f15aa26e3ab kernel: RDX: 7f1553ffe050 RSI: 4020ae46 RDI: 002f kernel: RBP: 5602a885a410 R08: 5602a82ad000 R09: 7f154c087470 kernel: R10: R11: 0246 R12: 7f1553ffe050 kernel: R13: 7f1553ffe160 R14: R15: 0080 kernel: The error occurred randomly in different production environments of the customer, all with the same call trace. Therefore, the likelihood of other processes contaminating memory is low. After analyzing the call trace with the help of debug symbols, we can pinpoint the source of the error. root@focal:~/ddeb# eu-addr2line -ifae ./usr/lib/debug/lib/modules/5.15.0-53-generic/kernel/arch/x86/kvm/kvm.ko __handle_changed_spte+0x3a9 0x00068109 __list_del inlined at /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 in __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:112:13 __list_del_entry /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:135:2 list_del /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/include/linux/list.h:146:2 tdp_mmu_unlink_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:305:2 handle_removed_tdp_mmu_page /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:340:2 __handle_changed_spte /build/linux-hwe-5.15-ZCQu4B/linux-hwe-5.15-5.15.0/arch/x86/kvm/mmu/tdp_mmu.c:491:3 The error occurred when the kernel attempted to delete an entry from a list. This issue may potentially be related to timing and has proven challenging to reproduce consistently, making it difficult for us to pinpoint the cause. It's worth noting that the current kernel has replaced the list_head with atomic_t, as indica
[Kernel-packages] [Bug 2035116] Re: allow io_uring to be disabled in runtime
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2035116 Title: allow io_uring to be disabled in runtime Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] io_uring has been an important attack vector in the recent years in local privilege escalation attacks. Allowing admins that don't use io_uring to disable it in their systems allows them to reduce their attack surface. [Test case] sysctl -w kernel.io_uring_disabled=1 then try to use io_uring from an unprivileged user, then try it with privileges (CAP_SYS_ADMIN) Actually also tried setting kernel.io_uring_disabled=2 and checking that neither (privileged or unprivileged worked). Then testing setting it back to 0. Then tested with io_uring_disabled set to 1 and io_uring_group=1000 and that it worked for group 1000, then set it to 1001 and verified that it didn't work anymore for group 1000. [Potential regression] Uses can be denied from using io_uring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034479] Re: Fix suspend hang on Lenovo workstation
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2034479 Title: Fix suspend hang on Lenovo workstation Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The system hang after resume from S3. Error logs: kernel: igb :02:00.0: disabling already-disabled device kernel: WARNING: CPU: 0 PID: 277 at drivers/pci/pci.c:2248 pci_disable_device+0xc4/0xf0 kernel: RIP: 0010:pci_disable_device+0xc4/0xf0 kernel: Call Trace: kernel: kernel: igb_io_error_detected+0x3e/0x60 kernel: report_error_detected+0xd6/0x1c0 kernel: ? __pfx_report_normal_detected+0x10/0x10 kernel: report_normal_detected+0x16/0x30 kernel: pci_walk_bus+0x74/0xa0 kernel: pcie_do_recovery+0xb9/0x340 kernel: ? __pfx_aer_root_reset+0x10/0x10 kernel: aer_process_err_devices+0x168/0x220 kernel: aer_isr+0x1b5/0x1e0 kernel: ? __pfx_irq_thread_fn+0x10/0x10 kernel: irq_thread_fn+0x21/0x70 kernel: irq_thread+0xf8/0x1c0 kernel: ? __pfx_irq_thread_dtor+0x10/0x10 kernel: ? __pfx_irq_thread+0x10/0x10 kernel: kthread+0xef/0x120 kernel: ? __pfx_kthread+0x10/0x10 kernel: ret_from_fork+0x29/0x50 kernel: kernel: ---[ end trace ]--- [Fix] The pci io error detected ops is called before the driver resumed. Avoid this race condition to fix the issue. [Test] Tested on hardware, the system suspend/resume OK. [Where problems could occur] It may break igb driver. The commit is included in 6.5-rc1 and merged by stable update in oem-6.1, SRU for Jammy and Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034745] Re: [regression] Unable to initialize SGX enclaves with XFRM other than 3
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034745 Title: [regression] Unable to initialize SGX enclaves with XFRM other than 3 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] In 5.15.0-1045, only loading enclaves with XFRM set to 3 works, sgx_encl_init returns EINVAL. The only reason this wouldn't work properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine in 5.15.0-1043. Likely cause: 1045 adds this patch: https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4 . This later patch indicates that the former patch introduced some ordering problems. https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5 . That later patch isn't applied to 1045. [Test Plan] User test results pending, but its a fix commit so should likely be applied regardless. [Regression Potential] SGX could continue to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Check for changes relevant for security certifications
This bug is awaiting verification that the linux/5.15.0-88.98 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-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. 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: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945989 Title: Check for changes relevant for security certifications Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Released 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 2038539] [NEW] bluetooth connections are unstable with linux-image-6.5.0-7-generic
Public bug reported: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Summary changed: - bluetooth connections are unstable with linux-image-6.5.0-7-gneric + bluetooth connections are unstable with linux-image-6.5.0-7-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-7-generic Status in linux package in Ubuntu: New Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 d
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-7-generic
did a whole fresh install to verify this .. initial kernel installed was 6.5.0-5 everything worked as expected .. upon upgrade to 6.5.0-7 the bluetooth connections became unstable .. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-7-generic Status in linux package in Ubuntu: New Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-7-generic
this is for the development version .. Mantic daily iso xubuntu 10-05-2023 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-7-generic Status in linux package in Ubuntu: New Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038539] 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/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC) Status in linux package in Ubuntu: Confirmed Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-7-generic
FYI the linux-image-6.5.0-6-genric version also has the bluetooth random disconnect/reconnect issue.. (using kubuntu or xubuntu instances .. all on the same physical hardware .. all Mantic ** Summary changed: - bluetooth connections are unstable with linux-image-6.5.0-7-generic + bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC) Status in linux package in Ubuntu: Confirmed Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038540] [NEW] Control generation of linux-source by default
Public bug reported: We tend to accidentally enable linux-source packages in new kernels. We need to ensure this defaults off by default. ** Affects: linux (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038540 Title: Control generation of linux-source by default Status in linux package in Ubuntu: In Progress Bug description: We tend to accidentally enable linux-source packages in new kernels. We need to ensure this defaults off by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038544] [NEW] MINT 21.2
Public bug reported: Kernel 5.15.06.0-86 Mint 21.2 Asus Vivobook 17 amd graphics. After login black screen. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038544 Title: MINT 21.2 Status in linux package in Ubuntu: Incomplete Bug description: Kernel 5.15.06.0-86 Mint 21.2 Asus Vivobook 17 amd graphics. After login black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038544] 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 2038544 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/2038544 Title: MINT 21.2 Status in linux package in Ubuntu: Incomplete Bug description: Kernel 5.15.06.0-86 Mint 21.2 Asus Vivobook 17 amd graphics. After login black screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038546] [NEW] /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64
Public bug reported: /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. ** Affects: linux-firmware (Ubuntu) Importance: High Status: Confirmed ** Tags: iso-testing mantic riscv64 ** Tags added: iso-testing mantic riscv64 ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2038546 Title: /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 Status in linux-firmware package in Ubuntu: Confirmed Bug description: /lib/firmware/brcm/brcmfmac43430-sdio.bin is needed for wifi on the StarFive VisionFive board which uses the starfive kernel flavor. The file was available in Jammy and only recently removed from Mantic. File debian/config/linux-firmware/riscv64/exclude.fwinfo is excluding it cyfmac43430-sdio.clm_blob which file WHENCE links to brcmfmac43430-sdio.bin. So this file needs to change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037065] Re: Wifi not working on StarFive VisionFive
*** This bug is a duplicate of bug 2038546 *** https://bugs.launchpad.net/bugs/2038546 ** This bug has been marked a duplicate of bug 2038546 /lib/firmware/brcm/brcmfmac43430-sdio.bin missing on riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive in Ubuntu. https://bugs.launchpad.net/bugs/2037065 Title: Wifi not working on StarFive VisionFive Status in linux-starfive package in Ubuntu: New Bug description: I am currently testing http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/20230920/mantic-preinstalled-server- riscv64+visionfive.img.xz according to http://iso.qa.ubuntu.com/qatracker/milestones/448/builds/287116/testcases/1754/results 'nmcli dev wifi list' and 'ip a' do not show the WiFi device. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-5.19.0-1014-starfive 5.19.0-1014.16 ProcVersionSignature: Ubuntu 5.19.0-1014.16-starfive 5.19.17 Uname: Linux 5.19.0-1014-starfive riscv64 ApportVersion: 2.27.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230920 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Sep 22 09:05:10 2023 ProcCpuinfoMinimal: processor: 1 hart : 0 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc SourcePackage: linux-starfive UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-starfive/+bug/2037065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036742] Re: amdgpu crash on Mantic
I don't expect it helps your boot issue, but the UBSAN issue will be fixed by this commit. https://lore.kernel.org/amd- gfx/78abc334-44ed-4632-8796-6bbe9c432...@amd.com/T/#me31ff6b88640b03be1a8edfc6fc8878ac78ca6bb Please redo the test with 5.15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036742 Title: amdgpu crash on Mantic Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Booting from USB the latest Mantic Desktop daily image (2023-09-20), just after the initial logs, nothing is displayed on screen. The system is still alive since _autoinstall_ works as intended. Once provisioned, the problem is still present. It seems related to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2029396 . dmesg attached. [Test Case] Live boot Ubuntu Mantic Desktop canary (2023-09-19) [Where Problems Could Occur] Dell Optiplex 5090 - Intel Core(TM) i7-11700 - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
** Description changed: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. + + Also we shomehow have remains of 440-server published in the archive, + with many superseeded (hostile takeover) of binary packages by + 450-server. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
As Rayen had changed the bug status from "Confirmed" to "Fix Released" by mistake, I just changed it back to the previous one, and hope that kernel team will now pay attention, work and release an appropriate fix for the above mentioned issues at the earliest. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 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-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
@vorlon I don't understand adding bumbleebee to this bug, as I am not requesting to remove it, and it has many aternative depends. These are updated in https://launchpad.net/ubuntu/+source/bumblebee/3.2.1-29ubuntu1 in proposed. ** Changed in: bumblebee (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
This bug was fixed in the package bumblebee - 3.2.1-29ubuntu1 --- bumblebee (3.2.1-29ubuntu1) mantic; urgency=medium * Drop old drivers from Ubuntu specific depends, keep just two latest series of drivers. LP: #2035189 -- Dimitri John Ledkov Thu, 05 Oct 2023 13:29:53 +0100 ** Changed in: bumblebee (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: Incomplete Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035189] Re: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers
** Changed in: nvidia-graphics-drivers-418-server (Ubuntu) Status: Incomplete => New ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2035189 Title: RM: EOL mantic nvidia-graphics-drivers - Remove from the archive, unmaintained upstream drivers Status in bumblebee package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Bug description: This legacy driver had the last update on 2022.11.22, and is EOL upstream. We should remove it from the archive before the next LTS, maybe even before Mantic is released. We're planning on migrating the kernel from fbdev drivers to using simpledrm, but this old driver doesn't support the fbdev emulation layer, meaning that VT's would remain blank when the driver is used. Similarly 418-server and 450-server are also EOL and unsupported. Also we shomehow have remains of 440-server published in the archive, with many superseeded (hostile takeover) of binary packages by 450-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/2035189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038508] Re: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dkms (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2038508 Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: Confirmed Bug description: xxx ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: willem 3916 F wireplumber /dev/snd/controlC1: willem 3916 F wireplumber /dev/snd/seq:willem 3902 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 5 09:13:13 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-10-21 (348 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. G752VM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VM.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: G dmi.product.name: G752VM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2038508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online
** Tags removed: rls-mm-incoming ** Changed in: systemd (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036968 Title: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online Status in cloud-images: New Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: Following a recent change from linux-kvm kernel to linux-generic kernel in the mantic minimized images, there is a reproducable bug where a guest VM does not have an IP address assigned as part of cloud-init provisioning. This is easiest to reproduce when emulating arm64 on amd64 host. The bug is a race condition, so there could exist fast enough virtualisation on fast enough hardware where this bug is not present but in all my testing I have been able to reproduce. The latest mantic minimized images from http://cloud- images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and no initrd to fallback to. This but is not present in the non minimized/base images @ http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with the required drivers present for virtio-net. Reproducer ``` wget -O "launch-qcow2-image-qemu-arm64.sh" https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh chmod +x ./launch-qcow2-image-qemu-arm64.sh wget https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image ./livecd.ubuntu-cpc.img ``` You will then be able to log in with user `ubuntu` and password `passw0rd`. You can run `ip a` and see that there is a network interface present (separate to `lo`) but no IP address has been assigned. ``` ubuntu@cloudimg:~$ 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: enp0s1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff ``` This is because when cloud-init is trying to configure network interfaces it doesn't find any so it doesn't configure any. But by the time boot is complete the network interface is present but cloud-init provisioning has already completed. You can verify this by running `sudo cloud-init clean && sudo cloud- init init` You can then see a successfully configured network interface ``` ubuntu@cloudimg:~$ 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: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1 valid_lft 86391sec preferred_lft 86391sec inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute valid_lft 86393sec preferred_lft 14393sec inet6 fe80::5054:ff:fe12:3456/64 scope link valid_lft forever preferred_lft forever ``` The bug is also reproducible with amd64 guest on adm64 host on older/slower hardware. The suggested fixes while debugging this issue are: * to include `virtio-net` as a built-in in the mantic generic kernel * understand what needs to change in cloud-init so that it can react to late additions of network interfaces I will file a separate bug against cloud-init to address the race condition on emulated guest/older hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035374] Re: pwr-mlxbf: update Kconfig with upstream changes
** Tags removed: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035374 Title: pwr-mlxbf: update Kconfig with upstream changes Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The Mellanox BlueField power driver (pwr-mlxbf) has a dependency on either the BlueField-2 or BlueField-3 GPIO driver. The current Kconfig does not have the BlueField-3 dependency. [Fix] There is an upstream commit that extends the Kconfig to include the GPIO_MLXBF3 dependency. [Test Case] Build the power driver with and without GPIO_MLXBF2 and GPIO_MLXBF3 present in the kernel configuration. Verify power driver is built. [Regression Potential] * none [Other] * none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038433] Re: systemd autopkgtest regression on arm64 and s390x on mantic
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038433 Title: systemd autopkgtest regression on arm64 and s390x on mantic Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux source package in Mantic: New Status in systemd source package in Mantic: New Bug description: tests-in-lxd seems to fail to download the lxd image used for the test (or something similar), looking at the log: ... Publishing instance: Image pack: 85% (5.51MB/s) Instance published with fingerprint: 83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114 6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+ 6845s autopkgtest [09:11:14]: version 5.28ubuntu1 6845s autopkgtest [09:11:14]: host autopkgtest; command line: /usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd autopkgtest/ubuntu/mantic/arm64 7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 'autopkgtest.XX'] failed (exit status 1, stderr '') 7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the testbed 7063s autopkgtest [09:14:52]: test tests-in-lxd: ---] 7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - 7064s tests-in-lxd FAIL non-zero exit status 1 2:40 PM ... This introduces a regression that is blocking the promotion of new kernels in Mantic. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: systemd 253.5-1ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0 Uname: Linux 6.5.0-5-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:38:15 2023 InstallationDate: Installed on 2023-09-25 (9 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.04 dmi.board.asset.tag: Default string dmi.board.name: G1621-02 dmi.board.vendor: GPD dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 2.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: G1621-02 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: GPD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038433] 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/2038433 Title: systemd autopkgtest regression on arm64 and s390x on mantic Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Mantic: Confirmed Status in systemd source package in Mantic: New Bug description: tests-in-lxd seems to fail to download the lxd image used for the test (or something similar), looking at the log: ... Publishing instance: Image pack: 85% (5.51MB/s) Instance published with fingerprint: 83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114 6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+ 6845s autopkgtest [09:11:14]: version 5.28ubuntu1 6845s autopkgtest [09:11:14]: host autopkgtest; command line: /usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd autopkgtest/ubuntu/mantic/arm64 7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 'autopkgtest.XX'] failed (exit status 1, stderr '') 7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the testbed 7063s autopkgtest [09:14:52]: test tests-in-lxd: ---] 7064s autopkgtest [09:14:53]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - - 7064s tests-in-lxd FAIL non-zero exit status 1 2:40 PM ... This introduces a regression that is blocking the promotion of new kernels in Mantic. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: systemd 253.5-1ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0 Uname: Linux 6.5.0-5-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:38:15 2023 InstallationDate: Installed on 2023-09-25 (9 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.04 dmi.board.asset.tag: Default string dmi.board.name: G1621-02 dmi.board.vendor: GPD dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 2.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: G1621-02 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: GPD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
SRU: https://lists.ubuntu.com/archives/kernel- team/2023-October/145972.html (unstable) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035971 Title: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision Status in linux package in Ubuntu: In Progress Bug description: Taking linux-kvm and linux-gcp for example: $ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | grep libcpupower -rw-r--r-- root/root103384 2023-07-25 20:00 ./usr/lib/libcpupower.so.6.2.0-1011 $ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb | grep libcpupower -rw-r--r-- root/root103392 2023-08-16 15:08 ./usr/lib/libcpupower.so.6.2.0-1011 linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain a libcpupower.so.6.2.0-1011 shared library used by their own cpupower utilities, and yet files of the same full path cannot be installed from two distinct debian packages, which follows we won't be able to install two linux-tools packages of two different derived kernels on the same system. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7 Uname: Linux 6.5.0-9004-generic x86_64 NonfreeKernelModules: zfs wl ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vicamo 6331 F wireplumber /dev/snd/controlC0: vicamo 6331 F wireplumber /dev/snd/seq:vicamo 6315 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Sep 14 23:31:16 2023 InstallationDate: Installed on 2022-04-10 (522 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-generic N/A linux-backports-modules-6.5.0-9004-generic N/A linux-firmware 20230815.git0e048b06-0ubuntu1 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2021 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 432.60.3.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038559] [NEW] package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post-installation script subprocess ret
Public bug reported: automated update of kernel package failed. Tooling says it will append details. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cabbey 3779 F wireplumber /dev/snd/controlC0: cabbey 3779 F wireplumber /dev/snd/controlC1: cabbey 3779 F wireplumber /dev/snd/seq:cabbey 3775 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Oct 3 20:26:20 2023 ErrorMessage: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2022-12-29 (279 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Micro-Star International Co., Ltd. MS-7B05 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=00c6269f-ccdd-4969-8e0c-162f71b4035c ro rootflags=subvol=@ intel_iommu=on vfio-pci.ids=10de:13c2,10de:0fbb Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to lunar on 2023-08-05 (61 days ago) dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.F0 dmi.board.asset.tag: Default string dmi.board.name: X299 TOMAHAWK (MS-7B05) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.F0:bd06/01/2020:br5.15:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B05:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299TOMAHAWK(MS-7B05):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B05 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038559 Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post- installation script subprocess returned error exit status 134 Status in linux package in Ubuntu: New Bug description: automated update of kernel package failed. Tooling says it will append details. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cabbey 3779 F wireplumber /dev/snd/controlC0: cabbey 3779 F wireplumber /dev/snd/controlC1: cabbey 3779 F wireplumber /dev/snd/seq:cabbey 3775 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Oct 3 20:26:20 2023 ErrorMessage: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2022-12-29 (279 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Micro-Star International Co., Ltd. MS-7B05 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=00c6269f-ccdd-4969-8e0c-162f71b4035c ro rootflags=subvol=@ intel_iommu=on vfio-pci.ids=10de:13c2,10de:0fbb Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to lunar on 2023-08-05 (61 days ago) dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.F0 dmi.board.asset.tag: Default string dmi.board.name:
[Kernel-packages] [Bug 2038559] 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/2038559 Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post- installation script subprocess returned error exit status 134 Status in linux package in Ubuntu: Confirmed Bug description: automated update of kernel package failed. Tooling says it will append details. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cabbey 3779 F wireplumber /dev/snd/controlC0: cabbey 3779 F wireplumber /dev/snd/controlC1: cabbey 3779 F wireplumber /dev/snd/seq:cabbey 3775 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Oct 3 20:26:20 2023 ErrorMessage: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2022-12-29 (279 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Micro-Star International Co., Ltd. MS-7B05 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=00c6269f-ccdd-4969-8e0c-162f71b4035c ro rootflags=subvol=@ intel_iommu=on vfio-pci.ids=10de:13c2,10de:0fbb Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: installed linux-image-6.2.0-34-generic package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to lunar on 2023-08-05 (61 days ago) dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.F0 dmi.board.asset.tag: Default string dmi.board.name: X299 TOMAHAWK (MS-7B05) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.F0:bd06/01/2020:br5.15:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B05:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX299TOMAHAWK(MS-7B05):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B05 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025054] Re: snap-kernel-uc22 lacks atheros firmware
** Tags added: pc-kernel ** Tags removed: pc-kernel ** Tags added: pc-kernel-snap -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025054 Title: snap-kernel-uc22 lacks atheros firmware Status in canonical-kernel-snaps: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Summary] The Atheros firmware files aren't available in the snap-kernel-uc22 snap, used in Ubuntu Core Desktop, so the Bluetooth module in Asus Zenbook UX21-e (and probably in a lot more devices) doesn't work. [Steps to reproduce] Boot, from a power-down state, a device with an Atheros-based Bluetooth module, into Ubuntu Core Desktop, open a root terminal and type bluetoothctl devices It returns the error 'No default controller available', because the Bluetooth module firmware wasn't loaded. Now, from a power-down state, boot into an Ubuntu live session (for example, from an USB pendrive), and when the desktop appears, reboot the computer (without powering it down) into Ubuntu Core Desktop and type again in a root terminal bluetoothctl devices This time there is no error, because the Bluetooth device firmware was already loaded in the Ubuntu live session. [Expected result] The call to `bluetoothctl devices` should not return any error. [Actual result] The call to `bluetoothctl devices` returns the 'No default controller available' error. [Failure rate] 3/3 [Stage] Patch available to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2025054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] [NEW] Mantic 6.5.0-7 kernel causes regression in LXD container usage
Public bug reported: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. >From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. ** Affects: ubuntu-release-notes Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs
[Kernel-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.10 ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Also affects: ubuntu-release-notes 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] 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 2038567 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
Current suspects are out of date apparmor features in livecd-rootfs pending https://launchpad.net/ubuntu/+source/livecd-rootfs/23.10.55 kernel, apparmor, snapd, lxd, snapd again having fits about all of them because of: .. Make snap "snapd" (20092) available to the system 2023-10-05T19:04:57Z INFO Requested daemon restart (snapd snap). .. Copy snap "lxd" data 2023-10-05T19:04:56Z ERROR unlinkat /var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo: function not implemented .. Run install hook of "lxd" snap if present 2023-10-05T19:04:55Z ERROR run hook "install": cannot read mount namespace identifier of pid 1: Permission denied and also because of: Oct 05 19:21:39 mantic-con-priv systemd[1]: snapd.service: Got notification message from PID 2560, but reception only permitted for main PID 2338 Oct 05 19:21:39 mantic-con-priv snapd[2338]: taskrunner.go:299: [change 7 "Setup snap \"snapd\" (20092) security profiles" task] failed: cannot reload udev rules: exit status 1 Oct 05 19:21:39 mantic-con-priv snapd[2338]: udev output: Oct 05 19:21:39 mantic-con-priv snapd[2338]: Failed to send reload request: No such file or directory Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Deactivated successfully. Oct 05 19:21:39 mantic-con-priv systemd[1]: snap-snapd-20092.mount: Unit process 2559 (snapfuse) remains running after unit stopped. Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading requested from client PID 2565 (unit snapd.service)... Oct 05 19:21:39 mantic-con-priv systemd[1]: Reloading... Oct 05 19:21:39 mantic-con-priv (sd-gens)[2568]: Read-only bind remount failed, ignoring: Permission denied and because of: Oct 05 19:20:58 cloudimg kernel: audit: type=1400 audit(1696533658.780:276): apparmor="DENIED" operation="mount" class="mount" info="failed type match" error=-13 profile="lxd-dominant- goldfish_" name="/snap/" pid=1940 comm="(sd- gens)" flags="ro, remount, bind" but could be util-linux too ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7
[Kernel-packages] [Bug 2038567] Re: Mantic 6.5.0-7 kernel causes regression in LXD container usage
apparmor side there are 2 immediate suspects. 1. kernel 0191e8433f76 UBUNTU: SAUCE: apparmor4.0.0: apparmor: Fix regression in mount mediation 2. userspace mount work to fix the mount CVE https://bugs.launchpad.net/apparmor/+bug/1597017 https://gitlab.com/apparmor/apparmor/-/merge_requests/1054 https://gitlab.com/apparmor/apparmor/-/merge_requests/333 I doubt #2 as this has been in the apparmor userspace in mantic since before 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/2038567 Title: Mantic 6.5.0-7 kernel causes regression in LXD container usage Status in Release Notes for Ubuntu: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Following upgrade to 6.5.0-7 kernel in mantic cloud images we are seeing a regression in our cloud image tests. The test runs the following: ``` lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait ``` The `lxc exec mantic -- cloud-init status --wait` times out after 240s and will fail our test as a result. I have been able to replicate in a local VM ``` wget http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img wget --output-document=launch-qcow2-image-qemu.sh https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt chmod +x launch-qcow2-image-qemu.sh ./launch-qcow2-image-qemu.sh --password passw0rd --image ./mantic-server-cloudimg-amd64.img cat < "./reproducer.sh" #!/bin/bash -eux lxd init --auto --storage-backend dir lxc launch ubuntu-daily:mantic mantic lxc info mantic lxc exec mantic -- cloud-init status --wait EOF chmod +x ./reproducer.sh sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -P ./reproducer.sh ubuntu@127.0.0.1:~/ sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get update sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 sudo apt-get upgrade --assume-yes sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -p ubuntu@127.0.0.1 ./reproducer.sh ``` The issue is not present with the 6.5.0-5 kernel and the issue is present regardless of the container launched. I tried the jammy container to test this. From my test VM ``` ubuntu@cloudimg:~$ uname --all Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ubuntu@cloudimg:~$ uname --kernel-release 6.5.0-7-generic ``` This is a regression in our test that will block 23.10 cloud image release next week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-azure/5.15.0-1050.57 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-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression
This bug is awaiting verification that the linux-aws/5.15.0-1048.53 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-jammy-linux-aws' to 'verification-done-jammy- linux-aws'. If the problem still exists, change the tag 'verification- needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'. 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: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036675 Title: 5.15.0-85 live migration regression Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Bug description: Fixes added for LP 2032164 [0] to resolve an issue in live migration have unfortunately introduced a regression, causing a previously working live migration pattern to fail when tested with the 5.15.0-85 kernel from -proposed. Specifically, live migration from a PKRU-enabled host running a kernel older than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail. The destination can be either with or without PKRU; both cases fail, although in different ways (one hangs, the other fails due to a PCID flag issue). The commits in question are commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0 Author: Dr. David Alan Gilbert Date: Mon Aug 21 14:47:28 2023 +0800 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES commit 27a189b881278c8ad9c16b0ee05668d724352733 Author: Leonardo Bras Date: Mon Aug 21 14:47:27 2023 +0800 x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0 [0] https://bugs.launchpad.net/bugs/2032164 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036377] Re: Fix RCU warning on AMD laptops
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036377 Title: Fix RCU warning on AMD laptops Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Scary kernel splat about RCU can be observed everytime laptop resumes from suspend. [Fix] Use non-atomic notifier for power supply change to relax the constraint. [Test] Once the fix is applied, no more RCU warning can be found after several suspend/resume cycle. [Where problems could occur] Essentially no regression potential. Atomic notifier should be used by core kernel, and things like power supply doesn't need to be atomic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1024.24 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-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. 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: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036184 Title: Infinite systemd loop when power off the machine with multiple MD RAIDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] The system with multiple MD RAIDs sometimes hangs while rebooting, that's because of the systemd can't stop and close the MD disk. [Fix] This commit fixes the issue, and this issue has been introduced by 12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed") after v6.0 https://patchwork.kernel.org/project/linux- raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/ [Test case] 1. Reboot the system with multiple MD RAIDs at least 10 times. 2. Make sure the system can reboot successfully every time. 3. You should not see error messages like below. [ 205.360738] systemd-shutdown[1]: Stopping MD devices. [ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127). [ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127, ignoring: Input/output error [ 205.404975] md: md127 stopped. [ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). [ 205.770179] md: md126: resync interrupted. [ 205.776258] md126: detected capacity change from 1900396544 to 0 [ 205.783349] md: md126 stopped. [ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125). [ 205.862435] md: md126 stopped. [ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125, ignoring: Input/output error [ 205.872845] block device autoloading is deprecated and will be removed. [ 205.880955] md: md125 stopped. [ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7). [ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or resource busy [ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6). [ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or resource busy [ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124). [ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or resource busy [ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left. [Where problems could occur] It fixes the data race issue, should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-aws/5.15.0-1048.53 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-jammy-linux-aws' to 'verification-done-jammy- linux-aws'. If the problem still exists, change the tag 'verification- needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'. 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: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035181 Title: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [Impact] Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work with CO-RE") from stable update breaks the ubuntu_bpf test build and cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in ubuntu_kernel_selftests stopped working, as they require bpf selftest to be built first. The following is extracted from the commit message: The problem is the new offsetof() does not play nice with static asserts. Given that the context is a static assert (and CO-RE relocation is not needed at compile time), offsetof() usage can be replaced by restoring the original offsetof() definition as __builtin_offsetof(). [Test Plan] Build bpf selftest in tools/testing/selftests with the following command: make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \ clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/ The build can finish successfully with patched kernel source code. [Where problems could occur] Fix limited to testing tool, if this fix is incorrect the bpf selftest build will remain broken. == Original bug report == Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04 This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84 is a security cycle, in which the ubuntu_bpf test was not triggered there) Test build failed with: CLNG-BPF [test_maps] test_btf_map_in_map.o CLNG-BPF [test_maps] test_btf_newkv.o CLNG-BPF [test_maps] test_btf_nokv.o CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o CLNG-BPF [test_maps] test_cgroup_link.o CLNG-BPF [test_maps] test_check_mtu.o CLNG-BPF [test_maps] test_cls_redirect.o make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' progs/test_cls_redirect.c:90:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv4.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof' #define offsetof(type, member) ((unsigned long)&((type *)0)->member) ^ progs/test_cls_redirect.c:95:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv6.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note:
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This bug is awaiting verification that the linux-azure/5.15.0-1050.57 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-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2035181 Title: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [Impact] Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work with CO-RE") from stable update breaks the ubuntu_bpf test build and cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in ubuntu_kernel_selftests stopped working, as they require bpf selftest to be built first. The following is extracted from the commit message: The problem is the new offsetof() does not play nice with static asserts. Given that the context is a static assert (and CO-RE relocation is not needed at compile time), offsetof() usage can be replaced by restoring the original offsetof() definition as __builtin_offsetof(). [Test Plan] Build bpf selftest in tools/testing/selftests with the following command: make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \ clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/ The build can finish successfully with patched kernel source code. [Where problems could occur] Fix limited to testing tool, if this fix is incorrect the bpf selftest build will remain broken. == Original bug report == Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04 This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84 is a security cycle, in which the ubuntu_bpf test was not triggered there) Test build failed with: CLNG-BPF [test_maps] test_btf_map_in_map.o CLNG-BPF [test_maps] test_btf_newkv.o CLNG-BPF [test_maps] test_btf_nokv.o CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o CLNG-BPF [test_maps] test_cgroup_link.o CLNG-BPF [test_maps] test_check_mtu.o CLNG-BPF [test_maps] test_cls_redirect.o make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' progs/test_cls_redirect.c:90:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv4.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33: note: expanded from macro 'offsetof' #define offsetof(type, member) ((unsigned long)&((type *)0)->member) ^ progs/test_cls_redirect.c:95:2: error: static_assert expression is not an integral constant expression sizeof(flow_ports_t) != ^~~ progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a reinterpret_cast is not allowed in a constant expression offsetofend(struct bpf_sock_tuple, ipv6.dport) - ^ progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend' (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER))) ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-azure/5.15.0-1050.57 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-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_sa
[Kernel-packages] [Bug 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
This bug is awaiting verification that the linux-aws/5.15.0-1048.53 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-jammy-linux-aws' to 'verification-done-jammy- linux-aws'. If the problem still exists, change the tag 'verification- needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'. 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: kernel-spammed-jammy-linux-aws-v2 verification-needed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034447 Title: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Seeing a panic on hidon (an Nvidia H100) after booting the 5.15.0-85-generic kernel: [ 58.935877] [ cut here ] [ 58.935893] refcount_t: underflow; use-after-free. [ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 refcount_warn_saturate+0xf7/0x150 [ 58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 dca xhci_pci intel_pmt drm [ 58.936077] pci_hyperv_intf i2c_ismt i2c_smbus [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936080] QAT: Could not find a device on node 1 [ 58.936083] mdio [ 58.936096] xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg [ 58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 5.15.0-85-generic #95-Ubuntu [ 58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023 [ 58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150 [ 58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f [ 58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282 [ 58.936142] RAX: RBX: RCX: 0027 [ 58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: ff314dbbbf9e0580 [ 58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: ff4d5d94b2c7f9c0 [ 58.936153] R10: 0028 R11: 0001 R12: [ 58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: ff314cbfd24b4000 [ 58.936159] FS: 7fadd2f6c8c0() GS:ff314dbbbf9c() knlGS: [ 58.936163] CS: 0010 DS: ES: CR0: 80050033 [ 58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 00771ee0 [ 58.936171] DR0: DR1: DR2: [ 58.936174] DR3: DR6: fffe07f0 DR7: 0400 [ 58.936177] PKRU: 5554 [ 58.936179] Call Trace: [ 58.936184] [ 58.936188] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936204] ? show_trace_log_lvl+0x1d6/0x2ea [ 58.936212] ? crypto_mod_put+0x6b/0x80 [ 58.936225] ? show_regs.part.0+0x23/0x29 [ 58.936232] ? show_regs.cold+0x8/0xd [ 58.936239] ? refcount_warn_saturate+0xf7/0x150 [ 58.936246] ? __warn+0x8c/0x100 [ 58.936255] ? refcount_warn_saturate+0xf7/0x150 [ 58.936263] ? report_bug+0xa4/0xd0 [ 58.936274] ? down_trylock+0x2e/0x40 [ 58.936285] ? handle_bug+0x39/0x90 [ 58.936296] ? exc_invalid_op+0x19/0x70 [ 58.936301] ? asm_exc_invalid_op+0x1b/0x20 [ 58.936310] ? refcount_warn_saturate+0xf7/0x
[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements
This bug is awaiting verification that the linux-azure/5.15.0-1050.57 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-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. 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: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033122 Title: Request backport of xen timekeeping performance improvements Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Users, especially those on EC2, are encouraged to select tsc as their default clocksource. However, this requires manual tuning of the operating system. Kvm can determine if it safe to use the tsc, and will default to that instead of its pvclock when appropriate. This requests a backport of patch does the same for Xen instances. If appropriate, it's fine if this is applied to only the linux-aws branches. Not all Xen EC2 instances advertise explicit nomigrate support, however, on those that do we'll select tsc by default. On the subset of hosts where this is advertised, users will safely default to the more performant clocksource. [Impact] Xen instances default to the xen clocksource which has been documented to be slower. This is required for instances where the tsc is not safe to use, or the guest is subject to migration. On some platforms the performance impact can be high, and users are encouraged to select the tsc when appropriate. Instead of leaving up to users to figure this out by reading a variety of different documents, pick the fast clocksource when it can be determined to be safe to do so. [Backport] Clean cherry pick. No conflicts applying to 5.15 or 6.2. [Test] Booted EC2 xen instances with and without this patch and validated that on those that properly advertised the required criteria via cpuid, that the clocksource defaulted to tsc instead of xen. [Potential Regression] Potential is low, since only absurd configurations could lead to a problem. If this is considered risky, it can be applied to only linux-aws where the documented guidance is for users to enable tsc as the clocksource on Xen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp