[Bug 2152688] Re: core103 failed to handle oversized command 0xC05

** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Questing) Importance: Undecided Status: New ** Changed in: backport-iwlwifi-dkms (Ubuntu Questing) Status: New => Invalid ** Changed in: backport-iwlwifi-dkms (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Questing) Status: New => Invalid ** Changed in: linux (Ubuntu Resolute) Status: New => Incomplete ** Changed in: linux (Ubuntu Stonking) Status: New => Incomplete ** Changed in: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => Incomplete ** Changed in: linux-oem-6.17 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.17 (Ubuntu Questing) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Stonking) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Questing) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Status: New => Incomplete ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-7.0 (Ubuntu Stonking) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152688 Title: core103 failed to handle oversized command 0xC05 Status in backport-iwlwifi-dkms package in Ubuntu: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Noble: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Incomplete Status in linux-oem-7.0 source package in Noble: Invalid Status in backport-iwlwifi-dkms source package in Questing: Invalid Status in linux source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux-oem-7.0 source package in Questing: Invalid Status in backport-iwlwifi-dkms source package in Resolute: Confirmed Status in linux source package in Resolute: Incomplete Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Incomplete Status in backport-iwlwifi-dkms source package in Stonking: Triaged Status in linux source package in Stonking: Incomplete Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: May 04 13:33:52 ubuntu-202603-38491 kernel: ------------[ cut here ]------------ May 04 13:33:52 ubuntu-202603-38491 kernel: Command UNKNOWN (0xc05) is too large (348 bytes) May 04 13:33:52 ubuntu-202603-38491 kernel: WARNING: CPU: 4 PID: 995 at drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/tx-gen2.c:1278 iwl_pcie_gen2_enqueue_hcmd+0x7ea/0xf10 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: Modules linked in: snd_soc_sof_sdw snd_sof_probes snd_soc_intel_hda_dsp_common qrtr snd_soc_rt722_sdca regmap_sdw_mbq snd_hda_codec_intelhdmi snd_soc_dmic bnep snd_hda_intel snd_sof_pci_intel_ptl snd_sof_pci_intel_lnl snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_hda_codec snd_hda_core snd_intel_dspcfg snd_intel_sdw_acpi snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi snd_hwdep intel_uncore_frequency soundwire_bus intel_uncore_frequency_common snd_soc_sdca x86_pkg_temp_thermal snd_soc_core intel_powerclamp snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_pcm kvm_intel snd_seq_midi dell_pc snd_ctl_led snd_seq_midi_event mei_gsc_proxy intel_rapl_msr binfmt_misc snd_rawmidi kvm xe uvcvideo dell_laptop May 04 13:33:52 ubuntu-202603-38491 kernel: snd_seq irqbypass videobuf2_vmalloc iwlmvm(O) uvc gpu_sched processor_thermal_device_pci videobuf2_memops polyval_clmulni btusb drm_gpuvm ghash_clmulni_intel videobuf2_v4l2 processor_thermal_device btrtl processor_thermal_wt_hint videobuf2_common aesni_intel dell_wmi drm_gpusvm_helper snd_seq_device platform_temperature_control mac80211(O) btintel drm_buddy dell_smbios snd_timer drm_ttm_helper processor_thermal_soc_slider btbcm videodev processor_thermal_rfim ttm btmtk dcdbas nls_iso8859_1 bluetooth libarc4 dell_wmi_ddv dell_wmi_sysman(+) dell_smm_hwmon mc firmware_attributes_class drm_exec iwlwifi(O) processor_thermal_rapl snd intel_rapl_common i2c_i801 processor_thermal_wt_req drm_suballoc_helper dell_wmi_descriptor wmi_bmof i2c_smbus processor_thermal_power_floor soundcore mei_me drm_display_helper processor_thermal_mbox crc8 i2c_mux mei cfg80211(O) cec intel_vpu rc_core iwlwifi_compat(O) intel_pmc_core platform_profile i2c_algo_bit igen6_edac pmt_telemetry int3403_thermal int340x_thermal_zone May 04 13:33:52 ubuntu-202603-38491 kernel: pmt_discovery pmt_class int3400_thermal intel_pmc_ssram_telemetry acpi_thermal_rel intel_vsec acpi_tad intel_hid sparse_keymap acpi_pad joydev input_leds serio_raw mac_hid sch_fq_codel msr parport_pc ppdev lp parport nvme_fabrics efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear uas usb_storage ucsi_acpi hid_multitouch typec_ucsi hid_generic typec nvme psmouse video intel_lpss_pci nvme_core e1000e nvme_keyring intel_lpss nvme_auth idma64 thunderbolt i2c_hid_acpi i2c_hid hid wmi pinctrl_intel_platform May 04 13:33:52 ubuntu-202603-38491 kernel: CPU: 4 UID: 0 PID: 995 Comm: NetworkManager Tainted: G O 6.17.0-1020-oem #20-Ubuntu PREEMPT(voluntary) May 04 13:33:52 ubuntu-202603-38491 kernel: Tainted: [O]=OOT_MODULE May 04 13:33:52 ubuntu-202603-38491 kernel: Hardware name: Dell Inc. Dell Pro 3 16 P316260/, BIOS 2.0.1 04/16/2026 May 04 13:33:52 ubuntu-202603-38491 kernel: RIP: 0010:iwl_pcie_gen2_enqueue_hcmd+0x7ea/0xf10 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: Code: ff ff ff 8b 5b 28 4c 89 e7 89 4d b0 89 de e8 dd 1f fd ff 8b 4d b0 89 da 48 c7 c7 d0 b2 d4 c0 48 89 c6 0f b7 c9 e8 c6 d8 68 f8 <0f> 0b c7 45 a4 ea ff ff ff e9 da fe ff ff 48 8b b5 48 ff ff ff 0f May 04 13:33:52 ubuntu-202603-38491 kernel: RSP: 0018:ffffd57e53ab2fc8 EFLAGS: 00010246 May 04 13:33:52 ubuntu-202603-38491 kernel: RAX: 0000000000000000 RBX: 0000000000000c05 RCX: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: RBP: ffffd57e53ab30a8 R08: 0000000000000000 R09: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8ef75ec60028 May 04 13:33:52 ubuntu-202603-38491 kernel: R13: 000000000000015c R14: 0000000000000c05 R15: 0000000000000001 May 04 13:33:52 ubuntu-202603-38491 kernel: FS: 0000789de8915580(0000) GS:ffff8efb03a6a000(0000) knlGS:0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 04 13:33:52 ubuntu-202603-38491 kernel: CR2: 00005bc50ada15f0 CR3: 000000012051d004 CR4: 0000000000f72ef0 May 04 13:33:52 ubuntu-202603-38491 kernel: PKRU: 55555554 May 04 13:33:52 ubuntu-202603-38491 kernel: Call Trace: May 04 13:33:52 ubuntu-202603-38491 kernel: <TASK> May 04 13:33:52 ubuntu-202603-38491 kernel: ? __wait_for_common+0x14d/0x180 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_schedule_timeout+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: ? bsearch+0x58/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_trans_pcie_send_hcmd+0x15b/0x470 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_trans_send_cmd+0x57/0xe0 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_send_cmd_pdu+0x53/0xa0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_uats_init+0x162/0x1d0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_up+0xa03/0xe80 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: __iwl_mvm_mac_start+0x227/0x2c0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: ? __iwl_mvm_mac_start+0x227/0x2c0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_mac_start+0x81/0x120 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: drv_start+0x52/0x120 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: ieee80211_do_open+0x333/0x800 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: ieee80211_open+0x6e/0xa0 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: __dev_open+0x136/0x300 May 04 13:33:52 ubuntu-202603-38491 kernel: __dev_change_flags+0x1b9/0x230 May 04 13:33:52 ubuntu-202603-38491 kernel: netif_change_flags+0x27/0x80 May 04 13:33:52 ubuntu-202603-38491 kernel: do_setlink.isra.0+0xb7c/0xea0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? _raw_spin_lock_irqsave+0xe/0x20 May 04 13:33:52 ubuntu-202603-38491 kernel: ? skb_queue_tail+0x48/0x60 May 04 13:33:52 ubuntu-202603-38491 kernel: ? sock_def_readable+0x52/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __netlink_sendskb+0x6a/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: ? netlink_unicast+0x35a/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __alloc_skb+0xd9/0x1b0 May 04 13:33:52 ubuntu-202603-38491 kernel: __rtnl_newlink+0x2ea/0x3c0 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnl_newlink+0x4ad/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __check_object_size.part.0+0x72/0x150 May 04 13:33:52 ubuntu-202603-38491 kernel: ? security_capable+0x44/0x80 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_rtnl_newlink+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnetlink_rcv_msg+0x37b/0x450 May 04 13:33:52 ubuntu-202603-38491 kernel: ? inode_set_ctime_to_ts+0x32/0xb0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_rtnetlink_rcv_msg+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_rcv_skb+0x59/0x110 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnetlink_rcv+0x15/0x30 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_unicast+0x28a/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_sendmsg+0x214/0x470 May 04 13:33:52 ubuntu-202603-38491 kernel: ____sys_sendmsg+0x36f/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: ___sys_sendmsg+0x99/0xf0 May 04 13:33:52 ubuntu-202603-38491 kernel: __sys_sendmsg+0x8c/0x100 May 04 13:33:52 ubuntu-202603-38491 kernel: __x64_sys_sendmsg+0x1d/0x30 May 04 13:33:52 ubuntu-202603-38491 kernel: x64_sys_call+0x237b/0x2680 May 04 13:33:52 ubuntu-202603-38491 kernel: do_syscall_64+0x80/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? fput_close_sync+0x3d/0xa0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __x64_sys_close+0x3e/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? proc_sys_write+0x13/0x20 May 04 13:33:52 ubuntu-202603-38491 kernel: ? vfs_write+0x29b/0x480 May 04 13:33:52 ubuntu-202603-38491 kernel: ? ksys_write+0xdb/0xf0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? irqentry_exit+0x43/0x50 May 04 13:33:52 ubuntu-202603-38491 kernel: ? exc_page_fault+0x90/0x1b0 May 04 13:33:52 ubuntu-202603-38491 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e May 04 13:33:52 ubuntu-202603-38491 kernel: RIP: 0033:0x789de952c06b May 04 13:33:52 ubuntu-202603-38491 kernel: Code: 48 89 e5 48 83 ec 20 89 55 ec 48 89 75 f0 89 7d f8 e8 f9 c4 f6 ff 8b 55 ec 48 8b 75 f0 41 89 c0 8b 7d f8 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 45 f8 e8 51 c5 f6 ff 48 8b May 04 13:33:52 ubuntu-202603-38491 kernel: RSP: 002b:00007fffd89c9080 EFLAGS: 00000293 ORIG_RAX: 000000000000002e May 04 13:33:52 ubuntu-202603-38491 kernel: RAX: ffffffffffffffda RBX: 00006220d400e430 RCX: 0000789de952c06b May 04 13:33:52 ubuntu-202603-38491 kernel: RDX: 0000000000000000 RSI: 00007fffd89c90c0 RDI: 000000000000000d May 04 13:33:52 ubuntu-202603-38491 kernel: RBP: 00007fffd89c90a0 R08: 0000000000000000 R09: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000000e May 04 13:33:52 ubuntu-202603-38491 kernel: R13: 00006220d400e430 R14: 0000000000000001 R15: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: </TASK> May 04 13:33:52 ubuntu-202603-38491 kernel: ---[ end trace 0000000000000000 ]--- May 04 13:33:52 ubuntu-202603-38491 kernel: iwlwifi 0000:00:14.3: Error sending UNKNOWN: enqueue_hcmd failed: -22 May 04 13:33:52 ubuntu-202603-38491 kernel: iwlwifi 0000:00:14.3: failed to send MCC_ALLOWED_AP_TYPE_CMD (-22) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2152688/+subscriptions

[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

Hi everyone, I just experienced the freeze firsthand on my bench while testing the latest update. The system went into suspension and completely failed to wake up, forcing me to hard-reboot. I managed to extract the kernel logs from that previous session using journalctl -b -1 -k and I'm attaching them here (log_crash_tonga.txt). As you can see, the kernel registers the wake-up triggers and even completes the suspend exit process (PM: suspend exit), but the display driver fails silently immediately after, cutting off any further video output or logging capability. This is running on an AMD Tonga/Polaris setup with Kernel 6.8.0-117-generic. Hopefully, this clean capture from the exact moment of the failure can help the maintainers pin down what is breaking the display pipeline during the resume phase. Best regards, Danilo (TheTongaGuy) ** Attachment added: "log_crash_tonga.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+attachment/5970632/+files/log_crash_tonga.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: Confirmed Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions

[Bug 2152695] Re: thunderbolt issue

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152695 Title: thunderbolt issue Status in linux package in Ubuntu: New Bug description: ThinkPad E16 Gen 3 After a shutdown, USB-C/Thunderbolt charging stopped working. Before this, boltd crashed once with SIGABRT. After reboot/shutdown, charging through the Thunderbolt/USB-C port no longer works. Kernel logs show: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed and: Firmware bug: duplicate port altmode SVID 0x17ef Thunderbolt service starts successfully afterward, but USB-C PD charging does not function. System: * Ubuntu 26.04 * Kernel 7.0.0-15-generic * Intel Gen14 platform * ThinkPad E16 Gen 3 The issue appeared immediately after shutdown/reboot sequence. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: sid 4176 F.... pipewire sid 4203 F.... wireplumber /dev/snd/seq: sid 4176 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:09:21 2026 InstallationDate: Installed on 2026-05-04 (11 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21SSS1HS00 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-7.0.0-15-generic root=UUID=10e4529a-ff25-4e9d-a309-b4eb9b41a841 ro rootflags=subvol=@ rootflags=subvol=@ quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-09 (6 days ago) dmi.bios.date: 08/20/2025 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: R30ET37W(1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 21SSS1HS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76485 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR30ET37W(1.11):bd08/20/2025:br1.11:efr1.11:svnLENOVO:pn21SSS1HS00:pvrThinkPadE16Gen3:rvnLENOVO:rn21SSS1HS00:rvrSDK0T76485WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21SS_BU_Think_FM_ThinkPadE16Gen3:pfaThinkPadE16Gen3: dmi.product.family: ThinkPad E16 Gen 3 dmi.product.name: 21SSS1HS00 dmi.product.sku: LENOVO_MT_21SS_BU_Think_FM_ThinkPad E16 Gen 3 dmi.product.version: ThinkPad E16 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152695/+subscriptions

[Bug 2152716] Re: iwlwifi: Microcode SW error detected (NMI_INTERRUPT_UMAC_FATAL) - Intel Wireless 9260

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152716 Title: iwlwifi: Microcode SW error detected (NMI_INTERRUPT_UMAC_FATAL) - Intel Wireless 9260 Status in linux package in Ubuntu: New Bug description: When I browse the internet, from time to time I lose the connection. I have to disable the wifi and enable it again after the iwlwifi crashes to be able to browse again. Hardware: Intel Wireless 9260 Firmware: 9260-th-b0-jf-b0-46.ucode. firmware version: 46.7e3e4b69.0 9260-th-b0-jf-b0-46.ucode ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 15 13:26:52 2026 InstallationDate: Installed on 2023-07-24 (1026 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Daten Tecnologia Ltda DC2A-T ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-generic root=UUID=c561caf0-d813-4ea4-b0d6-bffd781c6b12 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (1 days ago) dmi.bios.date: 10/23/2020 dmi.bios.release: 5.14 dmi.bios.vendor: Daten Tecnologia Ltda dmi.bios.version: DA301A dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: DA3PRO dmi.board.vendor: Daten Tecnologia Ltda dmi.board.version: DC dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Daten Tecnologia Ltda dmi.chassis.version: Default string dmi.modalias: dmi:bvnDatenTecnologiaLtda:bvrDA301A:bd10/23/2020:br5.14:svnDatenTecnologiaLtda:pnDC2A-T:pvrDefaultstring:rvnDatenTecnologiaLtda:rnDA3PRO:rvrDC:cvnDatenTecnologiaLtda:ct3:cvrDefaultstring:skuMB1AV1VN003:pfaA-D300: dmi.product.family: A-D300 dmi.product.name: DC2A-T dmi.product.sku: MB1AV1VN003 dmi.product.version: Default string dmi.sys.vendor: Daten Tecnologia Ltda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152716/+subscriptions

[Bug 2152728] Re: Bluetooth adapter (Intel BE201) not recognized after upgrading to Kubuntu 26.04 (Kernel 7.0)

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152728 Title: Bluetooth adapter (Intel BE201) not recognized after upgrading to Kubuntu 26.04 (Kernel 7.0) Status in linux package in Ubuntu: New Bug description: Information: - OS: Kubuntu 26.04 LTS - KDE Plasma Version: 6.6.4 - KDE Frameworks Version: 6.24.0 - Qt Version: 6.10.2 - Kernel Version: 7.0.0-15-generic (64-bit) - Hardware: Dell Inc. Dell 16 Plus DB16250 - CPU: Intel Core Ultra 9 288V - Wi-Fi/Bluetooth Chip: Intel Corporation BE201 320MHz [8086:a840] (rev 10) Expected Behavior: Bluetooth should be operational, and the Intel BE201 controller should be detected by the system to allow connections to wireless devices. Actual Behavior: Since upgrading from Kubuntu 25.10 to 26.04, the Bluetooth adapter is completely missing from the KDE system settings ("No Bluetooth adapters found"), even though the bluetooth.service is active and running. This seems to be a kernel/driver regression with the Intel BE201 chip on Kernel 7.0. Steps to Reproduce: 1. Upgrade from Kubuntu 25.10 to 26.04 LTS on a Dell 16 Plus (Intel BE201). 2. Boot into Kubuntu (Kernel 7.0.0-15-generic). 3. Open KDE System Settings -> Bluetooth. 4. Note that no Bluetooth adapter is found. Terminal Outputs: $ lspci -knn | grep -iA3 net 00:14.3 Network controller [0280]: Intel Corporation BE201 320MHz [8086:a840] (rev 10) Subsystem: Intel Corporation Device [8086:40e0] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Fri 2026-05-15 20:26:18 CEST; 8min ago Docs: man:bluetoothd(8) Main PID: 1028 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─1028 /usr/libexec/bluetooth/bluetoothd mai 15 20:26:18 pout-dell16plusdb16250 bluetoothd[1028]: Bluetooth daemon 5.85 mai 15 20:26:18 pout-dell16plusdb16250 bluetoothd[1028]: Starting SDP server mai 15 20:26:18 pout-dell16plusdb16250 systemd[1]: Started bluetooth.service - Bluetooth service. mai 15 20:26:18 pout-dell16plusdb16250 bluetoothd[1028]: Bluetooth management interface 1.23 initialized ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri May 15 20:36:35 2026 InstallationDate: Installed on 2025-09-11 (246 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Daily amd64 (20250910) MachineType: Dell Inc. Dell 16 Plus DB16250 ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=9f2f947f-4603-4b2c-99c3-d83902ca827e ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-15 (0 days ago) dmi.bios.date: 02/04/2026 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 1CMM64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd02/04/2026:br1.11:efr1.8:svnDellInc.:pnDell16PlusDB16250:pvr:rvnDellInc.:rn1CMM64:rvrA00:cvnDellInc.:ct10:cvr:sku0D31:pfaDellLaptops: dmi.product.family: Dell Laptops dmi.product.name: Dell 16 Plus DB16250 dmi.product.sku: 0D31 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152728/+subscriptions

[Bug 2152733] Re: failed to build against 6.17 kernel: error: initialization of struct ieee80211_class::namespace

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152733 Title: failed to build against 6.17 kernel: error: initialization of struct ieee80211_class::namespace Status in linux package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Bug description: We're building linux-modules-iwlwifi-oem-6.17 from backport-iwlwifi- dkms/resolute, and bug 2148273 introduced a breakage while fixing build against 7.0 kernels: net/wireless/sysfs.c:176:22: error: initialization of ‘const void * (*)(const struct device *)’ from incompatible pointer type ‘const struct ns_common * (*)(const struct device *)’ [-Werror=incompatible-pointer-types]   176 | .namespace = wiphy_namespace,       | ^~~~~~~~~~~~~~~ net/wireless/sysfs.c:176:22: note: (near initialization for ‘ieee80211_class.namespace’) cc1: some warnings being treated as errors make[7]: *** [/usr/src/linux-headers-6.17.0-1020-oem/scripts/Makefile.build:287: net/wireless/sysfs.o] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152733/+subscriptions

[Bug 2152733] [NEW] failed to build against 6.17 kernel: error: initialization of struct ieee80211_class::namespace

Public bug reported: We're building linux-modules-iwlwifi-oem-6.17 from backport-iwlwifi- dkms/resolute, and bug 2148273 introduced a breakage while fixing build against 7.0 kernels: net/wireless/sysfs.c:176:22: error: initialization of ‘const void * (*)(const struct device *)’ from incompatible pointer type ‘const struct ns_common * (*)(const struct device *)’ [-Werror=incompatible-pointer-types]   176 | .namespace = wiphy_namespace,       | ^~~~~~~~~~~~~~~ net/wireless/sysfs.c:176:22: note: (near initialization for ‘ieee80211_class.namespace’) cc1: some warnings being treated as errors make[7]: *** [/usr/src/linux-headers-6.17.0-1020-oem/scripts/Makefile.build:287: net/wireless/sysfs.o] Error 1 ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Resolute) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Stonking) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Description changed: + We're building linux-modules-iwlwifi-oem-6.17 from backport-iwlwifi- + dkms/resolute, and bug 2148273 introduced a breakage while fixing build + against 7.0 kernels: + net/wireless/sysfs.c:176:22: error: initialization of ‘const void * (*)(const struct device *)’ from incompatible pointer type ‘const struct ns_common * (*)(const struct device *)’ [-Werror=incompatible-pointer-types] - 176 | .namespace = wiphy_namespace, - | ^~~~~~~~~~~~~~~ +   176 | .namespace = wiphy_namespace, +       | ^~~~~~~~~~~~~~~ net/wireless/sysfs.c:176:22: note: (near initialization for ‘ieee80211_class.namespace’) cc1: some warnings being treated as errors make[7]: *** [/usr/src/linux-headers-6.17.0-1020-oem/scripts/Makefile.build:287: net/wireless/sysfs.o] Error 1 ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux (Ubuntu Stonking) Importance: Undecided => High ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Stonking) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152733 Title: failed to build against 6.17 kernel: error: initialization of struct ieee80211_class::namespace Status in linux package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Bug description: We're building linux-modules-iwlwifi-oem-6.17 from backport-iwlwifi- dkms/resolute, and bug 2148273 introduced a breakage while fixing build against 7.0 kernels: net/wireless/sysfs.c:176:22: error: initialization of ‘const void * (*)(const struct device *)’ from incompatible pointer type ‘const struct ns_common * (*)(const struct device *)’ [-Werror=incompatible-pointer-types]   176 | .namespace = wiphy_namespace,       | ^~~~~~~~~~~~~~~ net/wireless/sysfs.c:176:22: note: (near initialization for ‘ieee80211_class.namespace’) cc1: some warnings being treated as errors make[7]: *** [/usr/src/linux-headers-6.17.0-1020-oem/scripts/Makefile.build:287: net/wireless/sysfs.o] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152733/+subscriptions

[Bug 2152546] [NEW] amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

Public bug reported: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152546 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: New Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152546/+subscriptions

[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system

Would 'apt install -t resolute-base linux-generic' work? Just guessing, replacing "proposed" with "base"... -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions

[Bug 2152259] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2152259/+attachment/5970184/+files/ProcCpuinfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152259 Title: RTL8852AE (PCIe WiFi + USB BT combo) Bluetooth Failure Status in linux package in Ubuntu: Incomplete Bug description: Hardware: HP Pavilion Gaming 15-ec2xxx Chip: RTL8852AE (PCIe WiFi + USB BT combo) Symptom: hci0: RTL: Read reg16 failed (-110) crash loop triggered by BT connection attempt Kernel: 6.17.0-23-generic --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: svrt_ubu 14754 F.... wireplumber /dev/snd/controlC0: svrt_ubu 14754 F.... wireplumber /dev/snd/seq: svrt_ubu 14749 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2025-08-01 (286 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: HP HP Pavilion Gaming Laptop 15-ec2xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-23-generic root=UUID=b46be3e7-1b67-4d08-af06-a62ab919461b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-23.23~24.04.1-generic 6.17.13 RelatedPackageVersions: linux-restricted-modules-6.17.0-23-generic N/A linux-backports-modules-6.17.0-23-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: noble Uname: Linux 6.17.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/23/2025 dmi.bios.release: 15.30 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88DE dmi.board.vendor: HP dmi.board.version: 96.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.34 dmi.modalias: dmi:bvnAMI:bvrF.30:bd04/23/2025:br15.30:efr96.34:svnHP:pnHPPavilionGamingLaptop15-ec2xxx:pvr:rvnHP:rn88DE:rvr96.34:cvnHP:ct10:cvrChassisVersion:sku471C4PA#ACJ: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec2xxx dmi.product.sku: 471C4PA#ACJ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152259/+subscriptions

[Bug 2143083] Re: [SRU] Duplicated entries in /proc//mountinfo

This bug was fixed in the package linux - 6.17.0-29.29 --------------- linux (6.17.0-29.29) questing; urgency=medium * questing/linux: 6.17.0-29.29 -proposed tracker (LP: #2151099) * CVE-2026-31419 - net: bonding: fix use-after-free in bond_xmit_broadcast() * CVE-2026-31431 - crypto: algif_aead - Revert to operating out-of-place - crypto: algif_aead - snapshot IV for async AEAD requests - crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption - crypto: authencesn - Fix src offset when decrypting in-place - crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl - crypto: algif_aead - Fix minimum RX size check for decryption * CVE-2026-31533 - net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption * CVE-2026-31504 - net: fix fanout UAF in packet_release() via NETDEV_UP race -- Manuel Diewald <manuel.diewald@canonical.com> Tue, 05 May 2026 15:53:32 +0200 ** Changed in: linux (Ubuntu Questing) Status: In Progress => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31419 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31431 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31504 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31533 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2143083 Title: [SRU] Duplicated entries in /proc/<pid>/mountinfo Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [ Impact ] Sometimes on a system that is mounting and unmounting filesystems frequently, for example running lots of docker containers, the size of /proc/1/mountinfo, can become very large -- 100s, to 1000s of entries or more -- with the vast majority being a single entry duplicated many times. This causes other problems on the system, due to systemd parsing the mount table whenever it changes, and eating up a lot of memory, for example [0]. Waiting long enough there are rare events where the length of mountinfo can go into the millions of lines and lead to OOM and kernel panics. [Fix] Christian Brauner submitted a patch on the mailing list[1] (now merged upstream [2]) which fixes the issue by a) using the unique mount ID as the pos for iterating the mounts b) updating to the pos of the iterator before returning [ Test Plan ] To test whether this issue occurs, it is sufficient to rapidly mount and unmount tmpfs rapidly and poll for duplicates in `/proc/1/mountinfo` this can be done for example by the following pair of scripts: repro.sh -------- #!/bin/bash counter=0 while true; do echo -n "." unique_name="tmpfs_$$_$counter" mkdir -p "/tmp/$unique_name" sudo mount -t tmpfs "$unique_name" "/tmp/$unique_name" sudo umount "/tmp/$unique_name" rmdir "/tmp/$unique_name" ((counter++)) sleep 0.1 done ------- has-bug.sh -------- #!/bin/bash THRESHOLD=100 WAIT_MIN=30 WAIT_SECONDS=$((WAIT_MIN * 60)) SECONDS=0 while ((SECONDS < WAIT_SECONDS)); do # Get mountinfo entries and count total mountinfo="$(cat /proc/1/mountinfo)" mountinfo_count=$(echo "$mountinfo" | wc -l) if ((mountinfo_count > THRESHOLD)); then echo "$(date): Mount count ($mountinfo_count) exceeds threshold ($THRESHOLD)" # Find and log duplicate mount points with their counts duplicates=$(echo "$mountinfo" | sort | uniq -cd) if [[ -n "$duplicates" ]]; then echo "Duplicate mounts :" echo "$duplicates" | while read -r count mountpoint; do echo " $mountpoint: $count occurrences" done fi exit 0 fi sleep 0.1 done exit 1 ------ In my testing, about 5 minutes is sufficient time for the bug to occur, so I've set the timeout to 30min in the test plan out of an abundance of caution. If the bug is present in the running kernel, `has-bug.sh` will print a message about duplicate entries and exit success, otherwise it will time out and exit with return code 1. The high level test plan is: 1. Run `has-bug.sh` and `repro.sh` on unpatched kernel. 2. Observe that bug is present 3. Upgrade to patched kernel and restart 4. Run `has-bug.sh` and `repro.sh` on unpatched kernel. 5. Observe that bug is no longer present [ Where problems could occur ] * The patch to fix this modifies how iterator position is tracked when iterating mounts. It therefore potentially affects anything that iterates through the mounts. [ Other Info ] [0]: https://github.com/systemd/systemd/issues/37939 [1]: https://lore.kernel.org/lkml/20260129-geleckt-treuhand-4bb940acacd9@brauner/ [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a403d7aa9074f527f064ef0806aaab38d14b07c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143083/+subscriptions

[Bug 2148768] Re: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution

Verified with inux-oem-6.17/6.17.0-1021.21 on new Dell Renegade/Huracan PTL platforms with CirrusLogic audio solution, Go to g-s-d and select sound --> output (speaker) --> Test, and click on "Front Left" and "Front Right". The audio sounds good from the single side channel. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148768 Title: Fix internal speaker fail to output left/right only on CS42L45+CS35L57 audio solution Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Dell Renegade/Huracan PTL platform with CirrusLogic audio solution CS42L45+CS35L57 only output on both channels but can't output on left/right only. [Fix] Fix the backport commit: ffcd44f1bedb ("ASoC: cs35l56: Support for reading speaker ID from on-chip GPIOs") which may cause the incorrect speaker to be involved. [Test Case] 1. Boot up the machine of new Dell Renegade/Huracan PTL platforms with CirrusLogic audio solution 2. Go to g-s-d and select sound --> output (speaker) --> Test, and click on "Front Left" and "Front Right" 3. Make sure the audio output is from left only and right only [Where problems could occur] It corrects the speaker ID identification for CirrusLogic amplifiers. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2148768/+subscriptions

[Bug 2150065] Re: Fix mic mute led on a HP EliteBook 6 G2a platform

This bug was fixed in the package linux-oem-6.17 - 6.17.0-1023.23 --------------- linux-oem-6.17 (6.17.0-1023.23) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1023.23 -proposed tracker (LP: #2151771) [ Ubuntu: 6.17.0-29.29 ] * questing/linux: 6.17.0-29.29 -proposed tracker (LP: #2151099) * CVE-2026-31419 - net: bonding: fix use-after-free in bond_xmit_broadcast() * CVE-2026-31431 - crypto: algif_aead - Revert to operating out-of-place - crypto: algif_aead - snapshot IV for async AEAD requests - crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption - crypto: authencesn - Fix src offset when decrypting in-place - crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl - crypto: algif_aead - Fix minimum RX size check for decryption * CVE-2026-31533 - net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption * CVE-2026-31504 - net: fix fanout UAF in packet_release() via NETDEV_UP race -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Fri, 08 May 2026 09:55:15 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: Fix Committed => Fix Released ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31419 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31431 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31504 ** CVE added: https://cve.org/CVERecord?id=CVE-2026-31533 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150065 Title: Fix mic mute led on a HP EliteBook 6 G2a platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: SRU Justification: [Impact] New HP platform with Realtek ALC236 audio solution fail to toggle the mic-mute led accordingly while the mic-mute function work w/o problem. This SRU includes fix for the particular SSID only (Goat) [Fix] Backport the upstream fix: cb78517e60cf (ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2a Laptops") [Test Case] 1. Boot up the machine of new HP platforms Goat 2. Press Fn+F6 for mic mute function 3. Click led lights up/down in according with the mic mute functions. [Where problems could occur] It fixes the quirk for particular SSIDs of the audio solution. No regression expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150065/+subscriptions