[Kernel-packages] [Bug 2003031] Re: [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only
** Tags removed: kinetic ** Tags added: mantic ** Tags added: fixed-in-linux-v6.9-rc1 fixed-upstream ** No longer affects: kwin (Ubuntu) ** No longer affects: mutter (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only + [i915] Using gnome-shell with a USB-C dock on Intel Tiger Lake causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: [i915] Using gnome-shell with a USB-C dock on Intel Tiger Lake causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only Status in GNOME Shell: New Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2003031/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2059804] Re: shell stop, logs out
*** This bug is a duplicate of bug 2003031 *** https://bugs.launchpad.net/bugs/2003031 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2003031, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 2003031 [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059804 Title: shell stop, logs out Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: 2024-03-29T11:15:58.111046+01:00 jan-dell gnome-shell[119359]: Page flip failed: drmModeAtomicCommit: Device or resource busy 2024-03-29T11:15:58.112153+01:00 jan-dell kernel: [72897.470882] [ cut here ] 2024-03-29T11:15:58.112161+01:00 jan-dell kernel: [72897.470886] adding CRTC not allowed without modesets: requested 0x2, affected 0x3 2024-03-29T11:15:58.112162+01:00 jan-dell kernel: [72897.470944] WARNING: CPU: 1 PID: 119384 at drivers/gpu/drm/drm_atomic.c:1476 drm_atomic_check_only+0x3bb/0x400 [drm] 2024-03-29T11:15:58.112163+01:00 jan-dell kernel: [72897.470985] Modules linked in: tls r8153_ecm cdc_ether usbnet r8152 mii hid_logitech_hidpp usbhid uhid veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter bridge stp llc nf_tables vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm rfcomm snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nfnetlink binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_ctl_led snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_hda_codec_realtek snd_soc_core snd_hda_codec_generic dell_rbtn snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_in tel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core x86_pkg_temp_thermal dell_laptop 2024-03-29T11:15:58.112165+01:00 jan-dell kernel: [72897.471019] intel_powerclamp snd_hwdep snd_pcm cmdlinepart kvm_intel iwlmvm spi_nor snd_seq_midi ee1004 mei_pxp mei_hdcp mtd intel_rapl_msr btusb uvcvideo joydev snd_seq_midi_event kvm btrtl btbcm mac80211 snd_rawmidi irqbypass videobuf2_vmalloc btintel uvc rapl snd_seq btmtk videobuf2_memops dell_wmi intel_cstate videobuf2_v4l2 libarc4 bluetooth snd_seq_device processor_thermal_device_pci_legacy videodev snd_timer processor_thermal_device videobuf2_common processor_thermal_rfim dell_smbios ecdh_generic ecc dcdbas iwlwifi ledtrig_audio mc snd dell_wmi_sysman i2c_i801 mei_me processor_thermal_mbox spi_intel_pci dell_wmi_descriptor firmware_attributes_class i2c_smbus wmi_bmof soundcore processor_thermal_rapl spi_intel intel_rapl_common cfg80211 mei intel_soc_dts_iosf igen6_edac int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel intel_hid sparse_keymap acpi_pad acpi_tad input_leds mac_hid serio_raw hid_multitouch coretemp msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 2024-03-29T11:15:58.112166+01:00 jan-dell kernel: [72897.471054] dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic drm_kms_helper ghash_clmulni_intel sha256_ssse3 sha1_ssse3 hid_generic aesni_intel rtsx_pci_sdmmc crypto_simd cryptd psmouse e1000e nvme rtsx_pci intel_lpss_pci drm intel_ish_ipc thunderbolt intel_lpss nvme_core ucsi_acpi idma64 intel_ishtp typec_ucsi xhci_pci nvme_common xhci_pci_renesas typec i2c_hid_acpi i2c_hid video hid wmi pinctrl_tigerlake 2024-03-29T11:15:58.112167+01:00 jan-dell kernel: [72897.471075] CPU: 1 PID: 119384 Comm: KMS thread Tainted: G U W OE 6.5.0-26-generic #26-Ubuntu 2024-03-29T11:15:58.112168+01:00 jan-dell kernel: [72897.471076] Hardware name: Dell Inc. Latitude 5520/0G60M3, BIOS 1.35.0 01/31/2024 2024-03-29T11:15:58.112168+01:00 jan-dell kernel: [72897.471077] RIP:
[Kernel-packages] [Bug 2059804] [NEW] shell stop, logs out
You have been subscribed to a public bug: 2024-03-29T11:15:58.111046+01:00 jan-dell gnome-shell[119359]: Page flip failed: drmModeAtomicCommit: Device or resource busy 2024-03-29T11:15:58.112153+01:00 jan-dell kernel: [72897.470882] [ cut here ] 2024-03-29T11:15:58.112161+01:00 jan-dell kernel: [72897.470886] adding CRTC not allowed without modesets: requested 0x2, affected 0x3 2024-03-29T11:15:58.112162+01:00 jan-dell kernel: [72897.470944] WARNING: CPU: 1 PID: 119384 at drivers/gpu/drm/drm_atomic.c:1476 drm_atomic_check_only+0x3bb/0x400 [drm] 2024-03-29T11:15:58.112163+01:00 jan-dell kernel: [72897.470985] Modules linked in: tls r8153_ecm cdc_ether usbnet r8152 mii hid_logitech_hidpp usbhid uhid veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter bridge stp llc nf_tables vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm rfcomm snd_seq_dummy snd_hrtimer overlay cmac algif_hash algif_skcipher af_alg bnep nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nfnetlink binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_ctl_led snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_hda_codec_realtek snd_soc_core snd_hda_codec_generic dell_rbtn snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_inte l_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core x86_pkg_temp_thermal dell_laptop 2024-03-29T11:15:58.112165+01:00 jan-dell kernel: [72897.471019] intel_powerclamp snd_hwdep snd_pcm cmdlinepart kvm_intel iwlmvm spi_nor snd_seq_midi ee1004 mei_pxp mei_hdcp mtd intel_rapl_msr btusb uvcvideo joydev snd_seq_midi_event kvm btrtl btbcm mac80211 snd_rawmidi irqbypass videobuf2_vmalloc btintel uvc rapl snd_seq btmtk videobuf2_memops dell_wmi intel_cstate videobuf2_v4l2 libarc4 bluetooth snd_seq_device processor_thermal_device_pci_legacy videodev snd_timer processor_thermal_device videobuf2_common processor_thermal_rfim dell_smbios ecdh_generic ecc dcdbas iwlwifi ledtrig_audio mc snd dell_wmi_sysman i2c_i801 mei_me processor_thermal_mbox spi_intel_pci dell_wmi_descriptor firmware_attributes_class i2c_smbus wmi_bmof soundcore processor_thermal_rapl spi_intel intel_rapl_common cfg80211 mei intel_soc_dts_iosf igen6_edac int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel intel_hid sparse_keymap acpi_pad acpi_tad input_leds mac_hid serio_raw hid_multitouch c oretemp msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 2024-03-29T11:15:58.112166+01:00 jan-dell kernel: [72897.471054] dm_crypt hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic drm_kms_helper ghash_clmulni_intel sha256_ssse3 sha1_ssse3 hid_generic aesni_intel rtsx_pci_sdmmc crypto_simd cryptd psmouse e1000e nvme rtsx_pci intel_lpss_pci drm intel_ish_ipc thunderbolt intel_lpss nvme_core ucsi_acpi idma64 intel_ishtp typec_ucsi xhci_pci nvme_common xhci_pci_renesas typec i2c_hid_acpi i2c_hid video hid wmi pinctrl_tigerlake 2024-03-29T11:15:58.112167+01:00 jan-dell kernel: [72897.471075] CPU: 1 PID: 119384 Comm: KMS thread Tainted: G U W OE 6.5.0-26-generic #26-Ubuntu 2024-03-29T11:15:58.112168+01:00 jan-dell kernel: [72897.471076] Hardware name: Dell Inc. Latitude 5520/0G60M3, BIOS 1.35.0 01/31/2024 2024-03-29T11:15:58.112168+01:00 jan-dell kernel: [72897.471077] RIP: 0010:drm_atomic_check_only+0x3bb/0x400 [drm] 2024-03-29T11:15:58.112169+01:00 jan-dell kernel: [72897.471096] Code: ff ff 8b 87 c0 02 00 00 45 31 ed 85 c0 0f 8f 1b fd ff ff e9 a0 fd ff ff 44 89 ca 44 89 ee 48 c7 c7 f0 fd 52 c0 e8 15 88 a6 e0 <0f> 0b 31 c0 eb 90 4c 8b 49 20 44 8b 41 60 4d 85 e4 74 05 4d 8b 64 2024-03-29T11:15:58.112170+01:00 jan-dell kernel: [72897.471098] RSP: 0018:aac4078dfc10 EFLAGS: 00010246 2024-03-29T11:15:58.112170+01:00 jan-dell kernel: [72897.471099] RAX: RBX: 9d90eb0ad800 RCX: 2024-03-29T11:15:58.112171+01:00 jan-dell kernel: [72897.471100] RDX: RSI: RDI: 2024-03-29T11:15:58.112172+01:00 jan-dell kernel: [72897.471101] RBP: aac4078dfc48 R08: R09: 2024-03-29T11:15:58.112172+01:00 jan-dell kernel: [72897.471101] R10: R11: R12: 9d90c22c80d0 2024-03-29T11:15:58.112173+01:00 jan-dell kernel: [72897.471102] R13: 0002 R14: 0004 R15: 00e0 2024-03-29T11:15:58.112173+01:00 jan-dell kernel: [72897.471103] FS: 7046d24036c0() GS:9d982f64() knlGS:
[Kernel-packages] [Bug 2059807] Re: Power management settings on Ryzen 7 5800H are missing
This is because amd-pstate is in active mode but nothing is tuning EPP most likely. Try to upgrade to this version of power profiles daemon: https://launchpad.net/~superm1/+archive/ubuntu/ppd Then you can change the power setting using the Gnome or kde GUI for it or by using powerprofilesctl. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059807 Title: Power management settings on Ryzen 7 5800H are missing Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: After the update to kernel 6.5, cpufreq no longer has options to set most governors or frequencies. The only available options are powersave and performance, but changing between them seem to have no effect. Consequently, the CPU temperature is always high: while with the 6.2 kernel it would idle at under 50°C, now with 6.5 it's idling at 65°C. Under a load that, with the 6.2 kernel, would result in around 80°C on CPU and 70°C on motherboard, now with the 6.5 it results in 100°C on both CPU and motherboard (I barely can touch the laptop because it gets so hot). To be able to use my laptop properly, I'm having to choose the 6.2 kernel on boot time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Mar 29 15:54:34 2024 InstallationDate: Installed on 2017-06-13 (2480 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2019-12-22 (1558 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059820] [NEW] package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1
Public bug reported: 每次开机 提示一个报错 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-6.5.0-26-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 16:19:20 2024 ErrorMessage: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2024-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059820 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: 每次开机 提示一个报错 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-generic-hwe-22.04:amd64: Remove linux-image-generic-hwe-22.04:amd64: Remove linux-image-6.5.0-26-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 16:19:20 2024 ErrorMessage: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2024-03-29 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: 已安装 linux-image-6.5.0-26-generic 软件包 pre-removal 脚本 子进程返回错误状态 1 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.5/+bug/2059820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059814] [NEW] Enable GDS in the 6.8 based linux-nvidia kernel
Public bug reported: GDS enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU. This direct path increases system bandwidth and decreases the latency and utilization load on the CPU. This functionality has been enabled in all previous kernel versions and needs to be in this kernel so there is no loss of functionality for users. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2059814 Title: Enable GDS in the 6.8 based linux-nvidia kernel Status in linux-nvidia package in Ubuntu: New Bug description: GDS enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU. This direct path increases system bandwidth and decreases the latency and utilization load on the CPU. This functionality has been enabled in all previous kernel versions and needs to be in this kernel so there is no loss of functionality for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2059814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
As a temporary workaround, you can fetch an updated release version of crun from their GitHub and save it into /usr/local/bin. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported Status in crun package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059807] [NEW] Power management settings on Ryzen 7 5800H are missing
Public bug reported: After the update to kernel 6.5, cpufreq no longer has options to set most governors or frequencies. The only available options are powersave and performance, but changing between them seem to have no effect. Consequently, the CPU temperature is always high: while with the 6.2 kernel it would idle at under 50°C, now with 6.5 it's idling at 65°C. Under a load that, with the 6.2 kernel, would result in around 80°C on CPU and 70°C on motherboard, now with the 6.5 it results in 100°C on both CPU and motherboard (I barely can touch the laptop because it gets so hot). To be able to use my laptop properly, I'm having to choose the 6.2 kernel on boot time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Mar 29 15:54:34 2024 InstallationDate: Installed on 2017-06-13 (2480 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2019-12-22 (1558 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059807 Title: Power management settings on Ryzen 7 5800H are missing Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: After the update to kernel 6.5, cpufreq no longer has options to set most governors or frequencies. The only available options are powersave and performance, but changing between them seem to have no effect. Consequently, the CPU temperature is always high: while with the 6.2 kernel it would idle at under 50°C, now with 6.5 it's idling at 65°C. Under a load that, with the 6.2 kernel, would result in around 80°C on CPU and 70°C on motherboard, now with the 6.5 it results in 100°C on both CPU and motherboard (I barely can touch the laptop because it gets so hot). To be able to use my laptop properly, I'm having to choose the 6.2 kernel on boot time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Mar 29 15:54:34 2024 InstallationDate: Installed on 2017-06-13 (2480 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2019-12-22 (1558 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059353] Re: kernel 6.5.0-26-generic causes 640x480 default resolution on aspeed (drm/ast) video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059353 Title: kernel 6.5.0-26-generic causes 640x480 default resolution on aspeed (drm/ast) video Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: The previous kernel 6.5.0-17 worked fine. With -26, the gdm login screen is only 640x480. I inspected the changelog from -17 to -26 and found '- Revert "drm/ast: report connection status on Display Port."' in the list. I found the reverted patch at https://www.spinics.net/lists/stable/msg682026.html. I then built the 6.5.0-26 package with the "report connection" patch added and the resulting kernel has the correct resolution now. Why was the "report connection" patch reverted? Can it please be put back in? Hardware tested - Supermicro SYS-241E-TNRTTP. lspci shows this info for the ASPEED video controller: 02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 52) 02:00.0 0300: 1a03:2000 (rev 52) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059795] [NEW] dpkg error: '-' has bad syntax
Public bug reported: When I ran 2024.03.04 Focal aws-5.15 through ADT testing I got a regression on nvidia-graphics-drivers-340 that looks different than the previous hinting. The test log had "dpkg: error: version '-' has bad syntax: revision number is empty". I have included the output log from that test with this bug report. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024.03.04 F aws-5.15 ADT nvidia-graphics-drivers-340 output" https://bugs.launchpad.net/bugs/2059795/+attachment/5760650/+files/2024.03.04%20F%20aws-5.15%20ADT%20nvidia-graphics-drivers-340%20output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059795 Title: dpkg error: '-' has bad syntax Status in linux package in Ubuntu: New Bug description: When I ran 2024.03.04 Focal aws-5.15 through ADT testing I got a regression on nvidia-graphics-drivers-340 that looks different than the previous hinting. The test log had "dpkg: error: version '-' has bad syntax: revision number is empty". I have included the output log from that test with this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051720]
Had the same issue. Somehow, after a long power-off and turning on again, Bluetooth managed to show up and the message was gone. Using an AX200 as well. Currently using kernel 6.8.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Comment bridged from LTC Bugzilla
--- Comment From jldo...@us.ibm.com 2024-03-29 11:18 EDT--- I tested to see if mkvterm was performing as expected with the kernel in focal-proposed, and the behavior was correct. Ritu in Novalink did as well. In addition to that, the kernel was installed on two different lpars, and another engineer within IBM performed basic tests and stress tests. All tests passed. HVCS is working as expected. Many 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence these are set to Invalid. * Meanwhile these requested commits have been added to other kernels and distros. __ ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: New => Confirmed ** Also affects: snapd Importance: Undecided Status: New ** Changed in: snapd Status: New => Confirmed ** Summary changed: - Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 + Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 ** No longer affects: linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 Status in snapd: Confirmed Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059788] Re: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installa
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2059788 Title: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules- nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I am trying to update ubuntu to 23.10 from 21.04 but it appears I have both versions installed at the same partation at the same time... Found Ubuntu 21.04 (21.04) on /dev/sda2 Adding boot menu entry for UEFI Firmware Settings ... sudo do-release-upgrade Checking for a new Ubuntu release No new release found. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 15:38:30 2024 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-12-15 (105 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.4.11 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2059788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059788] [NEW] package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-25-generic package post-instal
Public bug reported: I am trying to update ubuntu to 23.10 from 21.04 but it appears I have both versions installed at the same partation at the same time... Found Ubuntu 21.04 (21.04) on /dev/sda2 Adding boot menu entry for UEFI Firmware Settings ... sudo do-release-upgrade Checking for a new Ubuntu release No new release found. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 15:38:30 2024 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-12-15 (105 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.4.11 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-03-29 (0 days ago) ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2059788 Title: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules- nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: I am trying to update ubuntu to 23.10 from 21.04 but it appears I have both versions installed at the same partation at the same time... Found Ubuntu 21.04 (21.04) on /dev/sda2 Adding boot menu entry for UEFI Firmware Settings ... sudo do-release-upgrade Checking for a new Ubuntu release No new release found. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 15:38:30 2024 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-12-15 (105 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1.1 apt 2.4.11 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to mantic on 2024-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2059788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031164] Re: package linux-modules-nvidia-535-6.2.0-26-generic 6.2.0-26.26+2 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-26-generic package post-installa
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2031164 Title: package linux-modules-nvidia-535-6.2.0-26-generic 6.2.0-26.26+2 failed to install/upgrade: installed linux-modules- nvidia-535-6.2.0-26-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: I found my system triggering a warning that there is a bug so I thought it would be nice to report the same ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-modules-nvidia-535-6.2.0-26-generic 6.2.0-26.26+2 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 Uname: Linux 6.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 8 18:11:52 2023 ErrorMessage: installed linux-modules-nvidia-535-6.2.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-08-02 (8 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.2.0-26-generic 6.2.0-26.26+2 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-26-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2031164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983180]
I'd like to report one more instance of this bug. BUT perhaps more importantly pass on a condition that seems to trigger these ACPI errors at boot time (which you may or may not realize) and which might affect your continued approach to fixing. I use an old Dell t7400 and just recently decided to activate their TPM (trusted platform module) in my bios. I had never received any of these boot ACPI errors until I activated the TPM (which uses the broadcom LAN chip for crypto key generation). Immediately after activation, the ACPI errors unique to my system were reported at boot through dmesg. Upon deactivation AND DISABLING the TPM function (there are 2 distinct steps needed) the boot time ACPI errors cease being reported. === ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU7._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) ACPI Error: Aborting method \_PR.CPU6._PCT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU6._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) and repeated for each core to 0 .. ACPI Error: Aborting method \_PR.CPU0._PCT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) my relevant machine info Kernel: 5.15.0-100-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Desktop System: Dell product: Precision WorkStation T7400 v: N/A serial: Chassis: type: 7 serial: Mobo: Dell model: 0RW199 serial: BIOS: Dell v: A11 date: 04/30/2012 CPU: Info: 2x 4-core model: Intel Xeon E5450 bits: 64 type: MCP SMP smt: arch: Core Yorkfield rev: A cache: L1: 2x 256 KiB (512 KiB) L2: 2x 12 MiB (24 MiB) Speed (MHz): avg: 2693 high: 3591 min/max: 2000/3000 cores: 1: 3591 2: 2394 3: 2394 4: 2394 5: 3591 6: 2394 7: 2394 8: 2394 bogomips: 57457 Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx Network: Device-1: Broadcom NetXtreme BCM5754 Gigabit Ethernet PCI Express vendor: Dell driver: tg3 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0 chip-ID: 14e4:167a class-ID: 0200 = I hope this is useful information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized for method [_CPC] [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714640] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714651] No Local Variables are initialized for Method [_CPC] [0.714653] No Arguments are initialized for method [_CPC] [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714940] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714952] No Local Variables are initialized for Method
[Kernel-packages] [Bug 1981783]
I'd like to report one more instance of this bug. BUT perhaps more importantly pass on a condition that seems to trigger these ACPI errors at boot time (which you may or may not realize) and which might affect your continued approach to fixing. I use an old Dell t7400 and just recently decided to activate their TPM (trusted platform module) in my bios. I had never received any of these boot ACPI errors until I activated the TPM (which uses the broadcom LAN chip for crypto key generation). Immediately after activation, the ACPI errors unique to my system were reported at boot through dmesg. Upon deactivation AND DISABLING the TPM function (there are 2 distinct steps needed) the boot time ACPI errors cease being reported. === ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU7._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) ACPI Error: Aborting method \_PR.CPU6._PCT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU6._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) and repeated for each core to 0 .. ACPI Error: Aborting method \_PR.CPU0._PCT due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._PCT.CFGD], AE_NOT_FOUND (20210730/psargs-330) my relevant machine info Kernel: 5.15.0-100-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Desktop System: Dell product: Precision WorkStation T7400 v: N/A serial: Chassis: type: 7 serial: Mobo: Dell model: 0RW199 serial: BIOS: Dell v: A11 date: 04/30/2012 CPU: Info: 2x 4-core model: Intel Xeon E5450 bits: 64 type: MCP SMP smt: arch: Core Yorkfield rev: A cache: L1: 2x 256 KiB (512 KiB) L2: 2x 12 MiB (24 MiB) Speed (MHz): avg: 2693 high: 3591 min/max: 2000/3000 cores: 1: 3591 2: 2394 3: 2394 4: 2394 5: 3591 6: 2394 7: 2394 8: 2394 bogomips: 57457 Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx Network: Device-1: Broadcom NetXtreme BCM5754 Gigabit Ethernet PCI Express vendor: Dell driver: tg3 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0 chip-ID: 14e4:167a class-ID: 0200 = I hope this is useful information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059778] [NEW] package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: may be due to low disc space due to windows 10 update on dual boot system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 06:24:31 2024 ErrorMessage: installed linux-image-6.5.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-21 (616 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059778 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: may be due to low disc space due to windows 10 update on dual boot system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 06:24:31 2024 ErrorMessage: installed linux-image-6.5.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-21 (616 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 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.5/+bug/2059778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059778] Re: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059778 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: may be due to low disc space due to windows 10 update on dual boot system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 29 06:24:31 2024 ErrorMessage: installed linux-image-6.5.0-26-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-21 (616 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 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.5/+bug/2059778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999589] Re: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic
This is affecting J-hwe-6.5 openstack s390x instances since 6.5.0-14.14~22.04.1 ** Tags added: 6.5 jammy ** Tags added: sru-20240205 sru-20240304 ** Summary changed: - net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic + net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / 6.5 ** Summary changed: - net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / 6.5 + net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999589 Title: net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x 5.19 / J-hwe-6.5 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Confirmed Bug description: All of the sm4* ciper testcases are failing in net:tls for kinetic linux 5.19.0-27.28 These seem like new testcases that have not been run before. and this has only been seen as far as I am aware of on s390x - 21:31:48 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendfile ... 21:31:48 DEBUG| [stdout] # # tls.c:314:sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # not ok 197 tls.13_sm4_gcm.sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.send_then_sendfile ... 21:31:49 DEBUG| [stdout] # # tls.c:314:send_then_sendfile:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # send_then_sendfile: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # not ok 198 tls.13_sm4_gcm.send_then_sendfile 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_max ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_max:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_max: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # not ok 199 tls.13_sm4_gcm.recv_max 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.recv_small ... 21:31:49 DEBUG| [stdout] # # tls.c:314:recv_small:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # recv_small: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # not ok 200 tls.13_sm4_gcm.recv_small 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # not ok 201 tls.13_sm4_gcm.msg_more 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.msg_more_unsent ... 21:31:49 DEBUG| [stdout] # # tls.c:314:msg_more_unsent:Expected ret (-1) == 0 (0) 21:31:49 DEBUG| [stdout] # # msg_more_unsent: Test terminated by assertion 21:31:49 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # not ok 202 tls.13_sm4_gcm.msg_more_unsent 21:31:49 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_single ... 21:31:49 DEBUG| [stdout] # # tls.c:314:sendmsg_single:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_single: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # not ok 203 tls.13_sm4_gcm.sendmsg_single 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_fragmented ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_fragmented:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_fragmented: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # not ok 204 tls.13_sm4_gcm.sendmsg_fragmented 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_large ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_large:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_large: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # not ok 205 tls.13_sm4_gcm.sendmsg_large 21:31:50 DEBUG| [stdout] # # RUN tls.13_sm4_gcm.sendmsg_multiple ... 21:31:50 DEBUG| [stdout] # # tls.c:314:sendmsg_multiple:Expected ret (-1) == 0 (0) 21:31:50 DEBUG| [stdout] # # sendmsg_multiple: Test terminated by assertion 21:31:50 DEBUG| [stdout] # # FAIL tls.13_sm4_gcm.sendmsg_multiple 21:31:50 DEBUG| [stdout] # not ok 206
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
Verified fix on jammy (not focal, sorry). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.15/5.15.0.1057.63~20.04.1)
All autopkgtests for the newly accepted linux-meta-aws-5.15 (5.15.0.1057.63~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-aws-5.15/unknown (amd64, arm64) systemd/245.4-4ubuntu3.23 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1057.63)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1057.63) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1057.63~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1057.63~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046040] Re: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble
Changing the state to Won't fix, because of LP: #2059762. ** Changed in: linux (Ubuntu Noble) Status: Fix Released => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046040 Title: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Won't Fix Bug description: [Impact] Intel Trust Domain Extensions (TDX) protects guest VMs from malicious host and certain physical attacks. Linux 6.7 introduced the TDX support for the host to run confidential VMs (TDX guests). [Test case] We should probably define with Intel a proper test case to test this feature, since it requires special hardware/firmware support. [Fix] Enable CONFIG_INTEL_TDX_HOST in our generic kernel. [Regression potential] The TDX host support may introduce potential performance regressions, so we should probably do some performance evaluation with vs without CONFIG_INTEL_TDX_HOST enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
If the issue is fixed without the extra patch, I think we can ignore it, it was probably a false positive from UBSAN. Let's keep an eye on it and if it shows up again in the future we can do a test with my additional patch. Thanks for update! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: == Comment:- Kowshik Jois B S == ---Problem Description--- Below trace messges are observed in dmesg after every reboot. [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [0.475750] Freeing unused kernel image (initmem) memory: 8832K [0.507388] Checked W+X mappings: passed, no W+X pages found [0.507400] Run /init as init process [0.507403] with arguments: [0.507404] /init [0.507405] with environment: [0.507406] HOME=/ [0.507407] TERM=linux [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic [0.511892] [ cut here ] [0.511904] UBSAN: array-index-out-of-bounds in /build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17 [0.511909] index 0 is out of range for type 'char [*]' [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic #11-Ubuntu [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries [0.511921] Call Trace: [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.511931] [c6683650] [c0c7bc58] __ubsan_handle_out_of_bounds+0xc4/0x12c [0.511938] [c6683700] [c005d2a8] module_frob_arch_sections+0x4ec/0x8d0 [0.511943] [c66837e0] [c02b98cc] layout_and_allocate.isra.0+0x38/0x2a8 [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0 [0.511953] [c6683990] [c02baca8] init_module_from_file+0xb4/0x14c [0.511958] [c6683a70] [c02baf70] sys_finit_module+0x230/0x48c [0.511963] [c6683b80] [c0033248] system_call_exception+0xe8/0x240 [0.511967] [c6683e50] [c000d15c] system_call_vectored_common+0x15c/0x2ec [0.511972] --- interrupt: 3000 at 0x7879b903b8a8 [0.511977] NIP: 7879b903b8a8 LR: CTR: [0.511980] REGS: c6683e80 TRAP: 3000 Not tainted (6.8.0-11-generic) [0.511984] MSR: 8000f033 CR: 48222428 XER: [0.511993] IRQMASK: 0 GPR00: 0161 7fffd683b580 7879b9166d00 0004 GPR04: 7879b8e0c160 0004 0010 0004 GPR08: 0001 GPR12: 7879b99d3a00 2000 0002 GPR16: 1b5c7d7453e0 7fffd683ba68 GPR20: 1b5c82154ae0 1b5c82142360 GPR24: 7879b957f7b0 1b5c82154ae0 1b5c82142160 GPR28: 7879b8e0c160 0002 1b5c82154ae0 1b5c82142380 [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8 [0.512032] LR [] 0x0 [0.512034] --- interrupt: 3000 [0.512036] ---[ end trace ]--- [0.518326] systemd[1]: Inserted module 'autofs4' [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [0.521583] systemd[1]: Detected virtualization powervm. [0.521589] systemd[1]: Detected architecture ppc64-le. [0.521593] systemd[1]: Running in initrd. [0.521743] systemd[1]: No hostname configured, using default hostname. [0.521789] systemd[1]: Hostname set to . [0.521847] systemd[1]: Initializing machine ID from random generator. [0.600736] systemd[1]: Queued start job for default target initrd.target. Machine Type = P10 LPAR Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com ---Steps to Reproduce--- 1. reboot the system 2. Once the system is booted back, look at dmesg ---uname output--- Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le
[Kernel-packages] [Bug 2059762] [NEW] CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
Public bug reported:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic kernel, despite our attempt with
LP: #2046040.
[Fix]
Disable CONFIG_INTEL_TDX_HOST in the generic kernel, until upstream will
properly support this option with kexec.
[Regression potential]
The Intel host TDX feature won't be available in the generic kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059762
Title:
CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Bug description:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic kernel, despite our attempt with
LP: #2046040.
[Fix]
Disable CONFIG_INTEL_TDX_HOST in the generic kernel, until upstream
will properly support this option with kexec.
[Regression potential]
The Intel host TDX feature won't be available in the generic kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059762/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059106] Re: I can't install linux-image-6.5.0-26-generic on jammy-updates
Thank you! My issue has been resolved ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059106 Title: I can't install linux-image-6.5.0-26-generic on jammy-updates Status in linux package in Ubuntu: Confirmed Bug description: -I need install a package but after running the command sudo apt install . return error: linux-image-generic-hwe-22.04 : Depends: linux-image-6.5.0-26-generic but it is not going to be installed - Then, I continued to install linux-image-6.5.0-26-generic. An error occurred during unpacking: Preparing to unpack .../linux-image-6.5.0-26-generic_6.5.0-26.26~22.04.1_amd64.deb ... Unpacking linux-image-6.5.0-26-generic (6.5.0-26.26~22.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-6.5.0-26-generic_6.5.0-26.26~22.04.1_amd64.deb (--unpack): unable to open '/boot/vmlinuz-6.5.0-26-generic.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-image-6.5.0-26-generic_6.5.0-26.26~22.04.1_amd64.deb Although, I used root privileges when installing Help me! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt
> I'll also report back once I am able to test the new kernel. I had a try and I was able to install it today on Noble by pulling the deb packages for linux-image-unsigned-6.8.0-20-generic, linux- modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from Launchpad manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt
> this system has a single DIMM which was provided by framework: DDR5-5600 - 32GB (1 x 32GB) My system is 8GB, single stick, same speed 5600 MT/s, same company (A-DATA). > Restarting firefox temporarily resolves the issue. This behavior started to happen after I switched to X11. You're the first I've ever heard of this. Hopefully it's not present in Wayland. There is very little testing or development that happens in X11. > After setting UMA_Game_Optimized, I can confirm that (after 30 minutes of usage), the system appears far more stable. That's good to hear the workarounds improve things for you too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000791] Re: When my laptop wakes up from sleep, it displays a message each time
I found a fix https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000791 Title: When my laptop wakes up from sleep, it displays a message each time Status in linux package in Ubuntu: Confirmed Bug description: When my laptop wakes up from sleep, it displays a message each time: Message 0002007 (seq 11) timeout PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 return -110 chip reset Every time my laptop wakes up from sleep, there are more messages, and the messages are reset when it is rebooted. I have an acer laptop,i updated the bios to the latest version, it didn't work and i have the latest version of ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 18:47:00 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.19.0-26-generic, x86_64: installed GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2022-12-07 (23 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Acer Aspire A715-42G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=7683ad64-565f-4b56-9d11-27156bba9f9f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2022 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975444] Re: mt7921e wifi fails to resume after suspend
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Expired Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to:
[Kernel-packages] [Bug 1975444] Re: mt7921e wifi fails to resume after suspend
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744 https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744 I found a fix, see here -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975444 Title: mt7921e wifi fails to resume after suspend Status in linux package in Ubuntu: Expired Bug description: After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot. I'm using Ubuntu 22.04 LTS Jammy and my wifi card is: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz using `mt7921e` driver. This is what I can see in the logs: kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset kernel: mt7921e :02:00.0: Message 004e (seq 7) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 4) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT kernel: mt7921e :02:00.0: chip reset failed kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 12) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 11) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 10) timeout kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e :02:00.0: Failed to get patch semaphore kernel: mt7921e :02:00.0: Message 8010 (seq 9) timeout kernel: mt7921_start+0x25/0x70 [mt7921e] kernel: mt7921e :02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: PM: pci_legacy_suspend(): mt7921_pci_suspend+0x0/0x340 [mt7921e] returns -110 kernel: mt7921e :02:00.0: Message 4007 (seq 2) timeout kernel: mt7921_poll_rx+0x4f/0xe0 [mt7921e] kernel: mt7921e :02:00.0 wlp2s0: renamed from wlan0 NetworkManager: [1653237444.7259] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci:00/:00:02.2/:02:00.0/ieee80211/phy0/rfkill1) (driver mt7921e) kernel: mt7921e :02:00.0: Firmware init done kernel: mt7921_pci_driver_init+0x23/0x1000 [mt7921e] kernel: mt7921e :02:00.0: ASIC revision: 79610010 I really appreciate someone's help to fix this behaviour. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsoles 1932 F pulseaudio /dev/snd/controlC0: dsoles 1932 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-07 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: AZW SER Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=212b8944-a42a-41d8-add0-95aa98d374fb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: jammy wayland-session Uname: Linux 5.15.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/21/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.08_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.08_P3C6M43_B_Link:bd01/21/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default
[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume
** Changed in: hwe-next 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.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress 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 Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047389] Re: Fix AMDGPU crash on 6.5 kernel
** Changed in: hwe-next 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.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047389 Title: Fix AMDGPU crash on 6.5 kernel Status in HWE Next: Fix Released 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 Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] AMD GPU crash with a message: " cp queue preemption timeout". [Fix] Disable MCBP(mid command buffer preemption) by default as old Mesa hangs with it. [Test] Tested on hardware, play web video for more than 1 hour OK. [Where problems could occur] It may break AMD GPU. This issue is only reproduced on v6.5+ kernel versions and fixes in v6.6, so SRU for oem-6.5, mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
** Changed in: hwe-next 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.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: Fix Released 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: 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 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] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
It also concerns « regular » Ubuntu 24.04 The reboot or shutdown hangs on for minutes ( ~5 min ) on ( maybe ) unmounting some snap : Job run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount/stop running (4min / 4min 33s) I can also see this kind of warnings : evict_inodes inode ff721d78, i_count = 1, was skipped! ( maybe unrelated to this topic.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if dmi-sysfs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name dmi-sysfs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051727] Re: tcp: Add memory barrier to tcp_push()
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal-linux-
aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem
still exists, change the tag 'verification-needed-focal-linux-aws-5.15'
to 'verification-failed-focal-linux-aws-5.15'.
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-focal-linux-aws-5.15-v2
verification-needed-focal-linux-aws-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/2051727
Title:
tcp: Add memory barrier to tcp_push()
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
Recently a patch has been accepted on the Linux Kernel regarding the
TCP stack which fix an additional +40ms latency on ARM64 CPU
architecture without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/
Would be possible to include the following patch as part of Linux
image on the most recent and LTS maintained Ubuntu versions?
Patch:
```
---
net/ipv4/tcp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index ff6838ca2e58..7bce79beca2b 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
+ smp_mb__after_atomic();
}
/* It is possible TX completion already happened
* before we set TSQ_THROTTLED.
--
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054567] Re: Fix bpf selftests build failure after v5.15.139 update
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2054567 Title: Fix bpf selftests build failure after v5.15.139 update Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU justification [Impact] Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail call counting with bpf2bpf and data on stack" that affects one of the bpf kselftests (tailcall_bpf2bpf6). because LIBBPF_OPTS macro does not exists, it does not compile. Error below. [Fix] Initially, I thought cherry-picking commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS" would be the best, but upstream stable just reverted the commit that broke it. Hence the fix consists of cherry-picking this commit from stable upstream 5.15.49: Commit 62900d358c48 (Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on stack") [Test] This should be solved soon, but compileselftests debian rule does not compile bpf selftests. I tested it by using our regression testing tooling, but same results can be achieved by running: $ make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all KDIR=/usr/src/linux-headers-5.15.0--generic from the linux tree directory Without the fix, it fails to compile: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c: In function ‘test_tailcall_bpf2bpf_6’: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9: warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean ‘LIBBPF_API’? [-Wimplicit-function-declaration] 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^~~ | LIBBPF_API /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: error: ‘bpf_test_run_opts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: note: each undeclared identifier is reported only once for each function it appears in /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40: error: ‘topts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17: error: expected expression before ‘.’ token 823 | .data_in = _v4, | ^ make[1]: *** [Makefile:471: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o] Error 1 make: *** [Makefile:172: all] Error 2 With the fix, it compiles. [Regression potential] The only place this is being used is selftests, so the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced 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 Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1 cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2044822 SRU Justification: [Impact] Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 'unstable' by 'jiffies' and other watchdogs, and disabled [Fix] cherry-pick 233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets platform from upstream fixes this [Test Plan] This has been tested by intel, and has been upstreamed for a while. [Where problems could occur] This is a fairly narrow change, and extends a behaviour correction to cover up to 4-socket machines, rather than just 2 socket machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2053251 Title: performance: Scheduler: ratelimit updating of load_avg Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] Improve cache bouncing on tg->load_avg [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Sapphire Rapids Date HW is expected at Canonical: Component(s): Perf-Scalability Scheduler [Software Information] Target Version: 24.04 Target Kernel: TBD Commit IDs: 1528c661c24b sched/fair: Ratelimit update to tg->load_avg External Links: [Business Justification] [Testing guidance] [External ID] LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. This is not used in xenial, therefore for xenial we only replaced debian/dkms-versions with debian./dkms-versions [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script (where needed), in xenial:linux we don't have it 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056143] Re: block/loop: No longer allows to create partitions
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-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/2056143 Title: block/loop: No longer allows to create partitions Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == -- Impact -- In 22.04/Jammy with the GA 5.15 kernel there was an upstream change preventing partition table operations when GENHD_FL_NO_PART is set. 1a721de8489f "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" Beside of changing return codes and breaking some user-space that way this also causes loop block devices to no longer be able to have partitions manually created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent active partition scans. -- Fix -- This was changed in 5.19 (and thus Mantic is not affected) by introducing a separate flag to prevent those scans: b9684a71fca7 "block, loop: support partitions without scanning" The fix depends on a larger rewrite so it cannot be simply picked. The biggest change from the original is moving the check for the new flag into a helper function in genhd.h which checks whether a disk should be scanned for partitions. That function was dropped with the upstream rewrite and checking moved into the loop driver directly. But it felt like adjusting the helper was the better approach. Note: The upstream patch has a follow-up change submitted: 748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set" We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c: blk_add_partitions() checks disk_part_scan_enabled() which was where we added the check for the backport instead of modifying disk_scan_partitions() directly. -- Testcase -- $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% -- Regression Potential -- If things go wrong it might be other devices which no longer get scanned automatically or other issues with the loop block driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1057.63~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. 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-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-aws source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration). [Fix] The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b [Test Plan] AWS tested [Where problems could occur] By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command. [Other Info] SF: 00380449 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
Last observed on Lubuntu Noble Numbat 24.04 Daily Build noble-desktop- amd64.iso 2024-03-28 both in the Live USB boot and installed to SSD (eMMC). For some reason this build wont let me generated ubuntu-bug files as it reports *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Problem in linux-image-6.8.0-11-generic The problem cannot be reported: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 Status in linux package in Ubuntu: New Status in linux-meta package in Ubuntu: New Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if dmi-sysfs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name dmi-sysfs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051727] Re: tcp: Add memory barrier to tcp_push()
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-fips' to
'verification-done-jammy-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-aws-fips' to
'verification-failed-jammy-linux-aws-fips'.
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-fips-v2
verification-needed-jammy-linux-aws-fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051727
Title:
tcp: Add memory barrier to tcp_push()
Status in linux package in Ubuntu:
New
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
Recently a patch has been accepted on the Linux Kernel regarding the
TCP stack which fix an additional +40ms latency on ARM64 CPU
architecture without impacting other CPU types.
More information can be find in here:
https://lore.kernel.org/netdev/20240119190133.43698-1-dipi...@amazon.com/
Would be possible to include the following patch as part of Linux
image on the most recent and LTS maintained Ubuntu versions?
Patch:
```
---
net/ipv4/tcp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
index ff6838ca2e58..7bce79beca2b 100644
--- a/net/ipv4/tcp.c
+++ b/net/ipv4/tcp.c
@@ -722,6 +722,7 @@ void tcp_push(struct sock *sk, int flags, int mss_now,
if (!test_bit(TSQ_THROTTLED, >sk_tsq_flags)) {
NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPAUTOCORKING);
set_bit(TSQ_THROTTLED, >sk_tsq_flags);
+ smp_mb__after_atomic();
}
/* It is possible TX completion already happened
* before we set TSQ_THROTTLED.
--
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051727/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.5/6.5.0.1018.19~22.04.2)
All autopkgtests for the newly accepted linux-meta-azure-6.5 (6.5.0.1018.19~22.04.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-azure-6.5/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure-6.5 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1 cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054567] Re: Fix bpf selftests build failure after v5.15.139 update
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054567 Title: Fix bpf selftests build failure after v5.15.139 update Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU justification [Impact] Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail call counting with bpf2bpf and data on stack" that affects one of the bpf kselftests (tailcall_bpf2bpf6). because LIBBPF_OPTS macro does not exists, it does not compile. Error below. [Fix] Initially, I thought cherry-picking commit "libbpf: Rename DECLARE_LIBBPF_OPTS into LIBBPF_OPTS" would be the best, but upstream stable just reverted the commit that broke it. Hence the fix consists of cherry-picking this commit from stable upstream 5.15.49: Commit 62900d358c48 (Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on stack") [Test] This should be solved soon, but compileselftests debian rule does not compile bpf selftests. I tested it by using our regression testing tooling, but same results can be achieved by running: $ make -C linux/tools/testing/selftests TARGETS=bpf SKIP_TARGETS= clean all KDIR=/usr/src/linux-headers-5.15.0--generic from the linux tree directory Without the fix, it fails to compile: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c: In function ‘test_tailcall_bpf2bpf_6’: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:9: warning: implicit declaration of function ‘LIBBPF_OPTS’; did you mean ‘LIBBPF_API’? [-Wimplicit-function-declaration] 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^~~ | LIBBPF_API /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: error: ‘bpf_test_run_opts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:21: note: each undeclared identifier is reported only once for each function it appears in /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:822:40: error: ‘topts’ undeclared (first use in this function) 822 | LIBBPF_OPTS(bpf_test_run_opts, topts, | ^ /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/prog_tests/tailcalls.c:823:17: error: expected expression before ‘.’ token 823 | .data_in = _v4, | ^ make[1]: *** [Makefile:471: /root/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tailcalls.test.o] Error 1 make: *** [Makefile:172: all] Error 2 With the fix, it compiles. [Regression potential] The only place this is being used is selftests, so the risk is very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2044822 SRU Justification: [Impact] Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 'unstable' by 'jiffies' and other watchdogs, and disabled [Fix] cherry-pick 233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets platform from upstream fixes this [Test Plan] This has been tested by intel, and has been upstreamed for a while. [Where problems could occur] This is a fairly narrow change, and extends a behaviour correction to cover up to 4-socket machines, rather than just 2 socket machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053251 Title: performance: Scheduler: ratelimit updating of load_avg Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] Improve cache bouncing on tg->load_avg [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Sapphire Rapids Date HW is expected at Canonical: Component(s): Perf-Scalability Scheduler [Software Information] Target Version: 24.04 Target Kernel: TBD Commit IDs: 1528c661c24b sched/fair: Ratelimit update to tg->load_avg External Links: [Business Justification] [Testing guidance] [External ID] LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced 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 Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052827] Re: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2056475 Title: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-aws source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our latest generation instances with networking heavy workloads is up to a 25% performance regression (i.e. NGINX in a load-balancing configuration). [Fix] The mainline Linux kernel will now support IRQ moderation by default for ENA in the 6.9 kernel release via this patch: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b [Test Plan] AWS tested [Where problems could occur] By enabling adaptive coalescing, the default interrupt behaviour will by changed to be more adaptive, which shows improvements on heavy network workloads, but my change the behaviour and performance on other network workloads differently. Rather than handling the interrupts based off of a fixed amount of time elapsed, it will change to an adaptive based approach. There should be no negative impact on light workloads, and a positive impact on heavy work loads. If there is an impact though, this option can be disabled via the ethtool command. [Other Info] SF: 00380449 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2056475/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. This is not used in xenial, therefore for xenial we only replaced debian/dkms-versions with debian./dkms-versions [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script (where needed), in xenial:linux we don't have it 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056143] Re: block/loop: No longer allows to create partitions
This bug is awaiting verification that the linux-aws- fips/5.15.0-1057.63+fips1 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-fips' to 'verification-done-jammy-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-fips' to 'verification-failed-jammy-linux-aws-fips'. 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-fips-v2 verification-needed-jammy-linux-aws-fips -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056143 Title: block/loop: No longer allows to create partitions Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == -- Impact -- In 22.04/Jammy with the GA 5.15 kernel there was an upstream change preventing partition table operations when GENHD_FL_NO_PART is set. 1a721de8489f "block: don't add or resize partition on the disk with GENHD_FL_NO_PART" Beside of changing return codes and breaking some user-space that way this also causes loop block devices to no longer be able to have partitions manually created. This is because the loop block driver uses GENHD_FL_NO_PART to prevent active partition scans. -- Fix -- This was changed in 5.19 (and thus Mantic is not affected) by introducing a separate flag to prevent those scans: b9684a71fca7 "block, loop: support partitions without scanning" The fix depends on a larger rewrite so it cannot be simply picked. The biggest change from the original is moving the check for the new flag into a helper function in genhd.h which checks whether a disk should be scanned for partitions. That function was dropped with the upstream rewrite and checking moved into the loop driver directly. But it felt like adjusting the helper was the better approach. Note: The upstream patch has a follow-up change submitted: 748008e1da92 "block: don't add partitions if GD_SUPPRESS_PART_SCAN is set" We do _NOT_ need that in Jammy/5.15 because block/partitions/core.c: blk_add_partitions() checks disk_part_scan_enabled() which was where we added the check for the backport instead of modifying disk_scan_partitions() directly. -- Testcase -- $ fallocate -l 1G /tmp/blob $ LOOPDEV=$(sudo losetup --find --show /tmp/blob) $ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt mkpart primary 0% 100% -- Regression Potential -- If things go wrong it might be other devices which no longer get scanned automatically or other issues with the loop block driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] [NEW] Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04
Public bug reported: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: 24.04 6.8 hang kernel lubuntu noble numbat reboot shutdown xubuntu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: calamares (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Lubuntu Noble 24.04 Status in linux package in Ubuntu: New Status in linux-meta package in Ubuntu: New Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
