** Also 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/2158236 Title: Fix amdgpu hang in amdgpu_ctx_mgr_entity_flush during exec Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Fix Released Status in linux source package in Stonking: New Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] System hangs on amdgpu during exec. systemd blocked for 368s in D state in amdgpu_ctx_mgr_entity_flush (mutex_lock) via filp_close -> amdgpu_flush during do_close_on_exec -> load_elf_binary. Reproduces on 6.17.0-1020-oem. kernel: INFO: task systemd:16426 blocked for more than 368 seconds. kernel: Tainted: G O 6.17.0-1020-oem #20-Ubuntu kernel: task:systemd state:D pid:16426 kernel: mutex_lock kernel: amdgpu_ctx_mgr_entity_flush+0x46/0x1f0 [amdgpu] kernel: amdgpu_flush+0x26/0x50 [amdgpu] kernel: filp_flush+0x6f/0xb0 kernel: filp_close+0x14/0x30 kernel: do_close_on_exec+0xe7/0x140 kernel: begin_new_exec+0x1ab/0x420 kernel: load_elf_binary+0x32d/0xf40 [Fix] Cherry-pick upstream commits: - b18fc0ab837381 "drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify" - 930595df251c "drm/amdgpu: remove check for BO reservation add assert instead" Pass NULL ticket to amdgpu_vm_handle_moved in move_notify so the clear=true path is used, avoiding a PT update while another process's job is still running — the contention that blocks amdgpu_ctx_mgr_entity_flush. [Test Plan] Boot oem-6.17 on dual-GPU AMD system without P2P PCI; glxgears on GPU0, Xorg on GPU1 sharing a dmabuf. Without fix: systemd hung >368s in amdgpu_ctx_mgr_entity_flush. With fix: no hang. [Where problems could occur] changes only the ticket arg in amdgpu_dma_buf_move_notify; normal VM update path untouched. Risk limited to dmabuf move-notify sync on multi-GPU shared-BO setups. It may break amdgpu driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158236/+subscriptions
вторник
[Bug 2156858] Re: [SRU] Fix GPU throttling limits on Strix Halo
With 6.17.0-1029 OEM kernel, we’ve verified that under the same workload, Strix Halo systems no longer reboot unexpectedly. Mark this as verified. ** 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/2156858 Title: [SRU] Fix GPU throttling limits on Strix Halo Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2156858 [ Impact ] We found that setting power_dpm_force_performance_level to high and running heavy workload on Strix Halo platforms somehow makes it reboot. This is due to the throttling limits in amdgpu don't aligned with the power management firmware properly. [ Fix ] Cherry-pick the following commit: - 03b70e0d8aa26bab (drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range) which has been accepted since mainline v7.1 [ Test ] 1. Boot the kernel 2. Run the same compute workload on a Strix Halo system, and it shouldn't reboot. [ Where problems could occur ] If the driver throttles to aggressively this may impact performance, but this is safer than letting Strix Halo burn. [ Additional Information ] https://github.com/torvalds/linux/commit/03b70e0d8aa26bab89a0f1394c1c80a871925e42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156858/+subscriptions
[Bug 2156858] Re: [SRU] Fix GPU throttling limits on Strix Halo
** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux-oem-6.17 (Ubuntu Resolute) 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/2156858 Title: [SRU] Fix GPU throttling limits on Strix Halo Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2156858 [ Impact ] We found that setting power_dpm_force_performance_level to high and running heavy workload on Strix Halo platforms somehow makes it reboot. This is due to the throttling limits in amdgpu don't aligned with the power management firmware properly. [ Fix ] Cherry-pick the following commit: - 03b70e0d8aa26bab (drm/amd/pm: smu_v14_0_0: use SoftMin for gfxclk in set_soft_freq_limited_range) which has been accepted since mainline v7.1 [ Test ] 1. Boot the kernel 2. Run the same compute workload on a Strix Halo system, and it shouldn't reboot. [ Where problems could occur ] If the driver throttles to aggressively this may impact performance, but this is safer than letting Strix Halo burn. [ Additional Information ] https://github.com/torvalds/linux/commit/03b70e0d8aa26bab89a0f1394c1c80a871925e42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156858/+subscriptions
[Bug 1894611] Re: kmod in bionic can't parse hwe/cloud kernel signatures
[Expired for kmod (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kmod (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1894611 Title: kmod in bionic can't parse hwe/cloud kernel signatures Status in kmod package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: kmod in bionic can't parse hwe/cloud kernel signatures kmod 27 https://lwn.net/Articles/812803/ linxu v5.2-rc1 changed kernel module signatures, which bionic's kmod 24 cannot parse. Only kmod 27 gained that ability. But we have backported v5.3+ kernels to bionic, resulting in modinfo showing incomplete information about the kernel modules. Originally reported at: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2020-September/018781.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1894611/+subscriptions
[Bug 2152688] Re: iwlwifi failed to handle oversized command 0xC05
backport-iwlwifi-dkms/1:0~103.14434-gitdf6b5bf4-0ubuntu3.26.04.2 with linux-oem-7.0/resolute 1009: $ sudo dmesg|grep iwlwifi [ 3.371910] iwlwifi_compat: loading out-of-tree module taints kernel. [ 3.371918] iwlwifi_compat: module verification failed: signature and/or required key missing - tainting kernel [ 3.373388] Loading modules backported from iwlwifi [ 3.373391] iwlwifi-stack-public:release/core103:14434:6861514a [ 3.425935] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [ 3.454979] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x1080901 wfpm id 0x80005b20 [ 3.454988] iwlwifi 0000:00:14.3: PCI dev 4d40/4090, rev=0x4b1, rfid=0x2010d000 [ 3.454989] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz [ 3.458810] iwlwifi 0000:00:14.3: loaded firmware version 100.d6bb293f.0 bz-b0-gf-a0-100.ucode op_mode iwlmvm [ 3.955752] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000 [ 4.037212] iwlwifi 0000:00:14.3: base HW address: 84:5c:f3:bf:8b:6e [ 4.104881] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0 backport-iwlwifi-dkms/1:0~103.14434-gitdf6b5bf4-0ubuntu3.26.04.2 with linux-oem-6.17/noble 1026: $ sudo dmesg|grep iwlwifi [ 4.540644] iwlwifi_compat: loading out-of-tree module taints kernel. [ 4.540648] iwlwifi_compat: module verification failed: signature and/or required key missing - tainting kernel [ 4.550396] Loading modules backported from iwlwifi [ 4.550402] iwlwifi-stack-public:release/core103:14434:6861514a [ 4.703972] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [ 4.714935] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x1080901 wfpm id 0x80005b20 [ 4.714942] iwlwifi 0000:00:14.3: PCI dev 4d40/4090, rev=0x4b1, rfid=0x2010d000 [ 4.714943] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz [ 4.718339] iwlwifi 0000:00:14.3: loaded firmware version 100.09e46595.0 bz-b0-gf-a0-100.ucode op_mode iwlmvm [ 5.375352] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000 [ 5.456375] iwlwifi 0000:00:14.3: base HW address: 84:5c:f3:bf:8b:6e [ 5.521457] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0 ** Tags removed: verification-needed-resolute verification-needed-resolute-linux-oem-7.0 ** Tags added: verification-done-resolute verification-done-resolute-linux-oem-7.0 -- 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: iwlwifi failed to handle oversized command 0xC05 Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-hwe-7.0 package in Ubuntu: Invalid 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-hwe-7.0 source package in Noble: Triaged 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-hwe-7.0 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: Fix Committed Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Fix Released Status in backport-iwlwifi-dkms source package in Stonking: Fix Released Status in linux source package in Stonking: In Progress Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [SRU Justification] [Impact] With Intel AX211 wireless module installed on Intel Wildcat Lake platform, kernel warning with following errors are found at loading iwlwifi driver: ``` kernel: iwlwifi 0000:00:14.3: Error sending UNKNOWN: enqueue_hcmd failed: -22 kernel: iwlwifi 0000:00:14.3: failed to send MCC_ALLOWED_AP_TYPE_CMD (-22) ``` This are found in mainline kernels 7.0+ as they are the kernel versions for WCL support, as well as backport-iwlwifi core102, 103, 104 and 105. backport-iwlwifi master branch HEAD has been partially patched, but incomplete. [Fix] For backport-iwlwifi-dkms, in the master branch HEAD it has commit 5a3d01a7ea635 ("[BUGFIX] wifi: iwlwifi: mvm: avoid oversized UATS command copy"), which is incomplete that Intel gives an additional patch titled "wifi: iwlwifi: mvm: don't map the stack to DMA". These two patches combined equal to https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi- next.git/commit/?h=fixes&id=e0c121d545134af886b28c4c26d91abf5dd39c17 ("wifi: iwlwifi: mvm: avoid oversized UATS command copy"). However the later breaks builds against kernel < 7.0 and therefore it takes additional backport related to kmalloc_obj family from commit 4862faa9c3dd ("Merge remote-tracking branch 'auto/master'"). Later, it's found to cause another PHC register failure warning on kernels >= 7.0, and it takes backports related to settime64 from another commit 5076fafb8e33 ("Merge remote-tracking branch 'auto/master'"). For the linux kernel in-tree iwlwifi driver, Intel proposed a fix https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi- next.git/commit/?h=fixes&id=e0c121d545134af886b28c4c26d91abf5dd39c17 ("wifi: iwlwifi: mvm: avoid oversized UATS command copy") that is already in linux-next. While v7.0 has already commit 81d90d93d22ca ("wifi: iwlwifi: Implement settime64 as stub for MVM/MLD PTP") that fixes the PHC register problem, no additional fix is needed. [Test Plan] There are 4 cases: * linux-unstable-7.1/stonking * linux-generic-7.0/resolute * linux-oem-7.0/resolute * backport-iwlwifi-dkms/stoking - tested against linux-unstable-7.1/stonking * backport-iwlwifi-dkms/resolute - tested against linux-generic-7.0/resolute, linux-oem-7.0/resolute and linux-oem-6.17/noble To test kernel packages: 1. Install kernels from corresponding -proposed pocket. 2. Boot from some Intel Wildcat Lake platforms with an Intel AX211 wireless module installed. Here I use Intel WCL-U RVP. 3. The dmesg should gives no error but probe iwlwifi kernel module successfully. To test backport-iwlwifi-dkms packages: 1. Boot the testing kernel from some Intel Wildcat Lake platforms with an Intel AX211 wireless module installed. Here I use Intel WCL-U RVP. 2. Install kernels from corresponding -proposed pocket. 3. The corresponding kernel modules should be built automatically by dpkg triggers. Use `dkms status` to list built kernel versions. 4. Reboot into the same kernel. The dmesg should gives no error but probe iwlwifi kernel module successfully. [Where problems could occur] This changes the way that command object is handled using IWL_HCMD_DFL_NOCOPY to avoid buffer size checking. It doesn't really change runtime behavior or anything else. [Other Info] The patches for backport-iwlwifi-dkms are meant to be superseded by the ones in the master branch, so I did not cherry-pick the one from linux-next instead. Nominate backport-iwlwifi-dkms Resolute and Stonking, because they are versions with WCL support. Nominate linux/{Q,R}, linux-oem-7.0, linux-oem-6.17, because they are either 7.0 kernels or uses backport-iwlwifi-dkms/R. ========== original bug report ========== 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) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1522 F.... pipewire ubuntu 1527 F.... wireplumber /dev/snd/seq: ubuntu 1522 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.standard.hotfix.manifest ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04d-proposed-20260427-100 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2026-04-30 (15 days ago) InstallationMedia: Ubuntu OEM 24.04.4 LTS "Noble Numbat" - Release amd64 (20260423) IwConfig: lo no wireless extensions. enp0s31f6 no wireless extensions. wlp0s20f3 no wireless extensions. MachineType: Dell Inc. Dell Pro 3 16 P316260 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=ad40f208-dcb5-4e8e-96c2-c4bb5ebdb23c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 RelatedPackageVersions: linux-restricted-modules-6.17.0-1020-oem N/A linux-backports-modules-6.17.0-1020-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: noble Uname: Linux 6.17.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/16/2026 dmi.bios.release: 2.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd04/16/2026:br2.0:efr1.0:svnDellInc.:pnDellPro316P316260:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0DF5: dmi.product.family: Dell Pro Laptops dmi.product.name: Dell Pro 3 16 P316260 dmi.product.sku: 0DF5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2152688/+subscriptions
[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.
Hi Aaron and Jeff, Do we have progress for this bug? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions
[Bug 2158605] Re: The screen will show garbages by running glxgears fullscreen.
** Tags added: jira-stella-3470 oem-priority -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158605 Title: The screen will show garbages by running glxgears fullscreen. Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: New 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: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2158605 [Impact] Screen garbage can show when running glxgears fullscreen on affected Intel graphics systems. The Launchpad report says it happens about 1 in 3 runs. [Fix] Skip the SCANOUT flag and VM_BIND checks for external dma-buf imports in the xe display framebuffer setup and pin paths. For imported sg buffers, CPU caching is controlled by the exporter. The patch keeps the existing checks for local buffers. This patch is from upstream Patchwork, not yet merged: https://patchwork.freedesktop.org/patch/732636/ [Test Plan] Run the fullscreen glxgears test 10 times: $ glxgears -fullscreen Or run the matching checkbox test for the affected GPU: $ checkbox-cli run graphics/2_valid_glxgears_fullscreen_PCI_ID_<affected-gpu> Without patch: screen shows garbage during the fullscreen glxgears test. With patch: fullscreen glxgears completes without screen garbage. [Where problems could occur] Could break external dma-buf framebuffer setup in the xe display driver. If the sg-buffer exception is wrong, imported framebuffers could be accepted when they should be rejected. This could show as display corruption, failed framebuffer creation, or xe framebuffer pinning warnings. [Other Info] SRU target: linux-oem-6.17. The patch is not in an upstream kernel release yet. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2158605/+subscriptions
[Bug 2158501] Re: linux: enable CONFIG_EROFS_FS_PAGE_CACHE_SHARE
** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) 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/2158501 Title: linux: enable CONFIG_EROFS_FS_PAGE_CACHE_SHARE Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: [Impact] Currently EROFS already ships CONFIG_EROFS_FS_PAGE_CACHE_SHARE in linux 7.0 as an optional feature. since it's already shipped and users can choose to use it at runtime or not, I hope this feature could be enabled in both Ubuntu 26.10(Stonking Stingray), 26.04(Resolute Raccoon) and future Ubuntu versions. Also, since CONFIG_EROFS_FS_ONDEMAND has been removed in Linux 7.2 cycle (https://git.kernel.org/torvalds/c/c37460cd9b2fc). Since CONFIG_EROFS_FS_ONDEMAND conflicts with CONFIG_EROFS_FS_PAGE_CACHE_SHARE due to CONFIG_EROFS_FS_ONDEMAND deprecation at Linux 7.0. I hope CONFIG_EROFS_FS_ONDEMAND can be disabled in Ubuntu 26.10(Stonking Stingray). [Fix] In short, I hope CONFIG_EROFS_FS_PAGE_CACHE_SHARE=y and CONFIG_EROFS_FS_ONDEMAND is not set [Test plan] Build tested. [Where problems could occur] Very small risk of regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158501/+subscriptions
понедельник
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
** Attachment added: "Ubuntu_24_04_4_dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+attachment/5980567/+files/Ubuntu_24_04_4_dmesg.txt.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
Hi Jeff, Here I update the latest test result, using Ubuntu 24.04.4 updated with the nvidia-64k kernel (6.17.0-1021-nvidia-64k): The issue remains reproducible. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2159937] [NEW] ASUS X411UA hard-freezes after GDM blanks display on i915
Public bug reported: Hardware: - ASUS VivoBook S X411UA - Intel Core i7-8550U - Intel UHD Graphics 620, PCI ID 8086:5917, i915 - BIOS X411UA.310 - Internal 1920×1080 display Software: - Ubuntu 26.04 - Kernel 7.0.0-27-generic - GNOME/GDM using Wayland Steps to reproduce: 1. Boot to the GDM login screen. 2. Leave the machine idle until the display blanks. 3. The machine subsequently becomes completely unresponsive and requires a hard power-off. Moving the cursor delays both display blanking and the freeze. The issue reproduced repeatedly. The journal ends abruptly without a clean shutdown, OOM, storage, or thermal error. Before one freeze, the kernel repeatedly reported: workqueue: output_poll_execute hogged CPU workqueue: i915_hpd_poll_init_work [i915] hogged CPU Testing: - i915.enable_psr=0 alone did not fix the problem. - i915.enable_psr=0 i915.enable_dc=0 has remained stable during stress testing and display blanking so far. Expected result: The display blanks and wakes normally without affecting the system. Actual result: Display blanking leads to a complete system freeze. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Tue Jul 7 16:16:10 2026 InstallationDate: Installed on 2026-07-07 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 13d3:5a07 IMC Networks VGA UVC WebCam Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. X411UA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no username) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=be61cce7-c4dc-42f6-99ea-8d7847981abe ro i915.enable_psr=0 i915.enable_psr=0 i915.enable_dc=0 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UA.310:bd04/16/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX411UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBookS: dmi.product.family: VivoBook S dmi.product.name: X411UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159937 Title: ASUS X411UA hard-freezes after GDM blanks display on i915 Status in linux package in Ubuntu: New Bug description: Hardware: - ASUS VivoBook S X411UA - Intel Core i7-8550U - Intel UHD Graphics 620, PCI ID 8086:5917, i915 - BIOS X411UA.310 - Internal 1920×1080 display Software: - Ubuntu 26.04 - Kernel 7.0.0-27-generic - GNOME/GDM using Wayland Steps to reproduce: 1. Boot to the GDM login screen. 2. Leave the machine idle until the display blanks. 3. The machine subsequently becomes completely unresponsive and requires a hard power-off. Moving the cursor delays both display blanking and the freeze. The issue reproduced repeatedly. The journal ends abruptly without a clean shutdown, OOM, storage, or thermal error. Before one freeze, the kernel repeatedly reported: workqueue: output_poll_execute hogged CPU workqueue: i915_hpd_poll_init_work [i915] hogged CPU Testing: - i915.enable_psr=0 alone did not fix the problem. - i915.enable_psr=0 i915.enable_dc=0 has remained stable during stress testing and display blanking so far. Expected result: The display blanks and wakes normally without affecting the system. Actual result: Display blanking leads to a complete system freeze. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Tue Jul 7 16:16:10 2026 InstallationDate: Installed on 2026-07-07 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 13d3:5a07 IMC Networks VGA UVC WebCam Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: ASUSTeK COMPUTER INC. X411UA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no username) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=be61cce7-c4dc-42f6-99ea-8d7847981abe ro i915.enable_psr=0 i915.enable_psr=0 i915.enable_dc=0 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X411UA.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X411UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX411UA.310:bd04/16/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX411UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX411UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBookS: dmi.product.family: VivoBook S dmi.product.name: X411UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159937/+subscriptions
[Bug 2153159] Re: [Ubuntu 26.04] KVM: IBM Test Accelerator for Z (TAZ) not working properly
** Tags removed: verification-needed-resolute-linux ** Tags added: verification-done-resolute-linux ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153159 Title: [Ubuntu 26.04] KVM: IBM Test Accelerator for Z (TAZ) not working properly Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Bug description: [ Impact ] Enable IBM Test Accelerator for Z. [ Fix ] Backport the following patches from upstream: - 2623c96f1172 KVM: s390: only deliver service interrupt with payload - b0ad874d9852 KVM: s390: vsie: Allow non-zarch guests - a9640e2eb711 KVM: s390: vsie: Disable some bits when in ESA mode - c0dcada088ff KVM: s390: vsie: Accommodate ESA prefix pages - 4aebd7d5c72f KVM: s390: Add KVM capability for ESA mode guests [ Test Plan ] Launch a TAZ instance and confirm it can start and run ESA mode nested guests without generating program exceptions in either the TAZ instance or its guests. [ Regression Potential] While the ESA mode enablement is fully opt-in and poses no risk to existing workloads, the prefix bitfield adjustment and the suppression of zero-payload SCLP interrupts are global changes affecting all KVM/s390 guests. Either could impact existing z/Architecture guests. --- On Ubuntu 26.04, the IBM Test Accelerator for Z (TAZ) is not working, i.e. it results in program exceptions within the TAZ instance and/or the guests within it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2153159/+subscriptions
[Bug 2158860] Re: Fix Mic Mute LED no function on HP EliteBook
Verified on GNZA14-PV-SKU2A with linux-oem-6.17/6.17.0-1029.29 kernel, press Fn+F9/F9 to toggle the microphone mute function, when the led is on, the microphone is verified muted. When the LED is off, the microphone is verified unmuted. ** 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/2158860 Title: Fix Mic Mute LED no function on HP EliteBook Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New 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: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Audio mic-mute LED does not work on some HP EliteBook laptops. [Fix] Add ALC236_FIXUP_HP_GPIO_LED fixup for affected HP laptops. Upstream commit in v7.2-rc1: 6efb1897209a ("ALSA: hda/realtek: Add LED fixup for HP EliteBook 6 G2i Laptops") [Test Plan] Press the audio mute key to toggle the mute state. Without patch: Audio mute LED does not light up when muted. With patch: Audio mute LED lights up when muted. [Where problems could occur] Only some particular SSID would be applied for this quirk which is considered low risk of regression To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158860/+subscriptions