Tested with the 7.0.0-31.31 kernel in -proposed, it fixed the timeout issue. ** Tags removed: verification-needed-resolute-linux ** Tags added: verification-done-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158883 Title: TPM2 key creation commands time out on some Infineon modules Status in linux package in Ubuntu: New Status in linux source package in Resolute: In Progress Bug description: [Impact] TPM2 key creation commands time out on and off on some Intel platforms that use Infineon SLB9670 and SLB9672 TPM modules. A recent change cut the timeout for the key creation commands (CREATE_PRIMARY, CREATE, CREATE_LOADED) from 300 seconds down to 30 seconds. On affected hardware these commands sometimes take longer than 30 seconds, so they fail with a timeout. The failures show up a few times across hundreds of test runs. This affects the in-kernel TPM path, so anything that creates TPM keys (measured boot, key sealing, fwts/checkbox TPM tests) can hit it. [Fix] Restore the timeout for the three key creation commands back to 300 seconds. Upstream commit: de59d78e64039baa5fed455ddb905ba8263e7ede ("tpm: restore timeout for key creation commands") This reverts the timeout regression from: 207696b17f38 ("tpm: use a map for tpm2_calc_ordinal_duration()") which is in v6.19-rc6. [Test Plan] On affected hardware with tpm2-tools installed, create a primary key many times: $ sudo tpm2_createprimary -C o -g sha256 -G rsa4096 -c /tmp/prim.ctx Without patch: some runs fail, shows TPM command timeout errors for the create commands. With patch: all runs pass, no TPM timeout errors. [Where problems could occur] This touches the TPM2 command duration table in the tpm driver. The change only raises the allowed wait time, so it does not change command behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158883/+subscriptions
понедельник
[Bug 2163180] [NEW] ThinkPad P1 Gen 7 (Intel Meteor Lake) black screen after suspend (s2idle) on XUbuntu 26.04 Edit
Public bug reported: Exactly same as bug #2161937 but then on Xubuntu 26.04 fully updated. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161937 Suspend/resume consistently fails to restore the display on a Lenovo ThinkPad P1 Gen 7 with Intel 135H CPU (no dedicated GPU). The system appears to resume successfully (keyboard remains responsive, Caps Lock light toggles), but the internal display remains black. ThinkPad P1 Gen 7 / 21KVCTO1WW BIOS N48ET34W 1.21, EC N48HT28W Intel Meteor Lake-P Arc / i915 Ubuntu kernel 7.0.0-29-generic Only s2idle available Intermittent black display after suspend/resume Caps Lock LED reacts; TTY and external display do not recover i915: Timeout waiting for DDI BUF A; Timed out waiting for DP idle patterns; flip_done timed out; vblank and CRTC commit timeouts i915.enable_psr=0 does not help ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: dcr 2403 F.... pipewire dcr 2418 F.... wireplumber /dev/snd/seq: dcr 2403 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Aug 10 18:19:54 2026 InstallationDate: Installed on 2026-08-06 (4 days ago) InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21KVCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=74d2b5cc-421d-465a-91f7-631a38aec25f ro i915.enable_dc=0 quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET33W(1.20):bd03/02/2026:br1.20:efr1.15:svnLENOVO:pn21KVCTO1WW:pvrThinkPadP1Gen7:rvnLENOVO:rn21KVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KV_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KVCTO1WW dmi.product.sku: LENOVO_MT_21KV_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO ** 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/2163180 Title: ThinkPad P1 Gen 7 (Intel Meteor Lake) black screen after suspend (s2idle) on XUbuntu 26.04 Edit Status in linux package in Ubuntu: New Bug description: Exactly same as bug #2161937 but then on Xubuntu 26.04 fully updated. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161937 Suspend/resume consistently fails to restore the display on a Lenovo ThinkPad P1 Gen 7 with Intel 135H CPU (no dedicated GPU). The system appears to resume successfully (keyboard remains responsive, Caps Lock light toggles), but the internal display remains black. ThinkPad P1 Gen 7 / 21KVCTO1WW BIOS N48ET34W 1.21, EC N48HT28W Intel Meteor Lake-P Arc / i915 Ubuntu kernel 7.0.0-29-generic Only s2idle available Intermittent black display after suspend/resume Caps Lock LED reacts; TTY and external display do not recover i915: Timeout waiting for DDI BUF A; Timed out waiting for DP idle patterns; flip_done timed out; vblank and CRTC commit timeouts i915.enable_psr=0 does not help ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: dcr 2403 F.... pipewire dcr 2418 F.... wireplumber /dev/snd/seq: dcr 2403 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Mon Aug 10 18:19:54 2026 InstallationDate: Installed on 2026-08-06 (4 days ago) InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21KVCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=74d2b5cc-421d-465a-91f7-631a38aec25f ro i915.enable_dc=0 quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET33W(1.20):bd03/02/2026:br1.20:efr1.15:svnLENOVO:pn21KVCTO1WW:pvrThinkPadP1Gen7:rvnLENOVO:rn21KVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KV_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KVCTO1WW dmi.product.sku: LENOVO_MT_21KV_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163180/+subscriptions
[Bug 2163181] [NEW] [UBUNTU 24.04] openCryptoki: Fix for supporting CCA 8.4
You have been subscribed to a public bug: Description: For supporting the new CCA 8.4 version, a fix is needed for the openCryptoki package. Without this fix, the version cannot be determined correctly and the CCA host library version will be reported as invalid, potentially causing security problems. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-221013 severity-high targetmilestone-inin--- -- [UBUNTU 24.04] openCryptoki: Fix for supporting CCA 8.4 https://bugs.launchpad.net/bugs/2163181 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2161036] Re: [SRU] Fix incorrect boot_display reporting on multi-GPU systems
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161036 Title: [SRU] Fix incorrect boot_display reporting on multi-GPU systems Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux-oem-7.0 source package in Noble: New Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: New Status in linux-oem-7.0 source package in Resolute: Fix Committed Status in linux source package in Stonking: In Progress Status in linux-oem-6.17 source package in Stonking: New Status in linux-oem-7.0 source package in Stonking: New Bug description: [SRU Justification] [Impact] On multi-GPU systems, a VGA-compatible device that is not driving the display can incorrectly be reported as the primary graphics device through the boot_display sysfs attribute. [Fix] Apply upstream commit 596b3678326d3d1aed7c19423b6746f1ce09688a ("x86/video: Only fall back to vga_default_device() without screen info"). When framebuffer screen information is valid, use it exclusively to identify the primary device. Fall back to vga_default_device() only when no framebuffer has been set up. [Test Plan] Boot a multi-GPU system and verify that boot_display identifies only the GPU backing the framebuffer. Verify fallback behavior when no framebuffer has been initialized. [Where problems could occur] The change is limited to primary display-device detection in arch/x86/video/video-common.c. The main risk is incorrect identification of the primary GPU on systems with unusual or incomplete framebuffer information. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2161036/+subscriptions
[Bug 2161309] Re: Backlight regression
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Fix Committed Bug description: ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not 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: USER PID ACCESS COMMAND /dev/snd/controlC0: neal 3608 F.... wireplumber /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native 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: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions
[Bug 2161385] Re: Delta_Ubuntu24.04_Ubuntu (Waston)_Suspend(S3) Stress Test Fail when the A400 is on by remote controller .
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161385 Title: Delta_Ubuntu24.04_Ubuntu (Waston)_Suspend(S3) Stress Test Fail when the A400 is on by remote controller . Status in OEM Priority Project: 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: New Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Summary] Waston suspend stress Fail [Steps to reproduce] 1.Clean Install Ubuntu 24.04 OS. 2.Follow the instructions in the document "Linux Automation Testing Instruction.docx" to set up the test environment. 3.Execute the test case "TestCase_132157_Stress_Suspend(250 cycles)". 4.Issue occurs. [Expected result] All result pass [Actual result] show fail [Failure rate] 100% [Affected test cases] 160331 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2161385/+subscriptions
[Bug 2162012] Re: Backport: "firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits"
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162012 Title: Backport: "firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits" Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: New Status in linux-nvidia-7.0 package in Ubuntu: In Progress Status in linux-nvidia-bos package in Ubuntu: In Progress Status in linux-hwe-7.0 source package in Noble: In Progress Status in linux-nvidia-7.0 source package in Noble: New Status in linux-nvidia-bos source package in Noble: New Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: In Progress Status in linux-nvidia-7.0 source package in Resolute: New Status in linux-nvidia-bos source package in Resolute: New Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: New Status in linux-nvidia-7.0 source package in Stonking: In Progress Status in linux-nvidia-bos source package in Stonking: In Progress Bug description: [ Summary ] A recent stable-update pulled two v7.1 FF-A commits into the linux-nvidia 7.0 branches, but not the third commit in the chain. The result is that FF-A fails to initialise on 64K page kernels whose firmware rejects a 64K RX/TX buffer, taking every FF-A device with it. This backports the missing fix. ### The regression Stable-updates applied these two, both of which first shipped upstream in **v7.1**: | Backport | Upstream | BugLink | |---|---|---| | `7bfaed6b412b` firmware: arm_ffa: Use the correct buffer size during RXTX_MAP | `83210251fd70` | LP #2156385 | | `105dac1d2c92` firmware: arm_ffa: Align RxTx buffer size before mapping | `0399e3f872ca` | LP #2156390 | The first makes the driver advertise `PAGE_ALIGN(rxtx_bufsz)` to firmware; the second is its follow-up fix. Both landed in `Ubuntu-nvidia-bos-7.0.0-2016.16`, the most recent tag on this branch. Earlier tags are not affected. The third commit in the chain, which fixes the fallout from the first, only landed upstream in **v7.2-rc4**: 53716a4d745f firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits [ Impact ] On a 64K page kernel the driver takes the firmware advertised minimum RX/TX buffer size, rounds it up to `PAGE_SIZE`, and asks firmware to map that. FF-A implementations before v1.2 advertise no maximum and may simply reject the rounded up size. There is no clamp and no retry, so probe fails: ARM FF-A: Driver version 1.2 ARM FF-A: Firmware version 1.1 found ARM FF-A: failed to register FFA RxTx buffers and no FF-A devices are registered at all. Anything sitting on FF-A goes with it, including TPM over FF-A. Trigger is `PAGE_SIZE` greater than the advertised minimum, so the 64K flavours. Platforms with FF-A v1.2 or later firmware are unaffected, since the advertised maximum is then respected. [ Fix ] Backport of `53716a4d745f`. It decodes the maximum buffer size that FF-A v1.2+ reports, clamps the page aligned minimum to it, and where no maximum is advertised retries `RXTX_MAP` at the advertised minimum if the rounded size is rejected with `INVALID_PARAMETERS`. [ Test Plan ] Tested on an Arm server reporting FF-A firmware version 1.1, running a 64K page kernel built from this branch's own `nvidia-bos-64k` flavour annotations. Before, on the unmodified branch tip: ARM FF-A: failed to register FFA RxTx buffers /sys/bus/arm_ffa/devices/ -> empty After, with this commit applied: ARM FF-A: Firmware version 1.1 found ARM FF-A: Failed to create IRQ mapping! /sys/bus/arm_ffa/devices/ -> arm-ffa-1 .. arm-ffa-5 All five partitions enumerate again. The remaining "Failed to create IRQ mapping" line is pre-existing and also present on the distro kernel that predates the regression. No new BUG, WARNING or call traces. [ Where Problems Could Occur ] A regression in this fix could cause issues with the ARM FF-A driver's partition enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162012/+subscriptions
[Bug 2152688] Re: iwlwifi failed to handle oversized command 0xC05
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- 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: In Progress 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 Released 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 2156313] Re: Audio shows Dummy Output on systems with Cirrus Logic cs42l43 codec
This bug is awaiting verification that the linux/7.0.0-31.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156313 Title: Audio shows Dummy Output on systems with Cirrus Logic cs42l43 codec Status in linux package in Ubuntu: New 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: [Impact] Audio shows "Dummy Output" in GNOME and no input devices are available on Dell systems with a Cirrus Logic cs42l43 codec (SoundWire part_id 0x2A3B). The regression was introduced by commit 87a3f5c8ac20 (merged in v7.1-rc1), which moved spk:cs42l43-spk string generation into the generic asoc_sdw_rtd_init() path. That commit added component_name to the 0x4243 cs42l43 entry but missed the 0x2A3B entry. Without component_name on the 0x2A3B dp6 DAI, asoc_sdw_rtd_init() never appends "spk:cs35l56-bridge" to card->components. The sof-soundwire UCM regex then fails to match a speaker codec, all HiFi profiles are marked available=no, and WirePlumber falls back to the Off profile with no nodes. Hits 100% on affected hardware. [Fix] Add the missing .component_name = "cs42l43-spk" field to the 0x2A3B cs42l43 entry's AMP DAI in codec_info_list. The existing SOC_SDW_SIDECAR_AMPS redirect in asoc_sdw_rtd_init() then correctly translates this to "cs35l56-bridge" in card->components, which matches the UCM regex and the existing cs35l56-bridge.conf UCM file. This is an original fix; the same bug exists in linux-next and will be submitted upstream. https://lore.kernel.org/lkml/178127688584.48375.17454457885369484858.b4-ty@b4/ Fixes: 87a3f5c8ac20 ("ASoC: sdw_utils: cs42l43: allow spk component names to be combined") [Test Plan] Boot on affected Dell hardware with cs42l43 0x2A3B codec. Without patch: GNOME shows "Dummy Output", no microphone listed. With patch: 1. Check card->components includes spk: token: $ cat /sys/class/sound/card0/components | grep -o 'spk:[^ ]*' Expected: spk:cs35l56-bridge 2. Check WirePlumber selected HiFi profile: $ pw-cli enum-params <sof-soundwire-device-id> EnumProfile | grep -E 'index|available' Expected: active profile has available=yes 3. Test speaker output: $ speaker-test -c 2 -l 1 -t wav Expected: audio plays without error [Where problems could occur] Could affect snd-soc-sdw-utils and any machine using the cs42l43 0x2A3B codec with sidecar amps. If the sidecar redirect logic in asoc_sdw_rtd_init() misidentifies the component, the wrong spk: string could end up in card->components, causing UCM to select the wrong speaker init config. Speaker output would fail or use an incorrect routing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156313/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-191.201)
All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-191.201) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf, i386) nvidia-graphics-drivers-390/unknown (amd64) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
воскресенье
[Bug 2092703] Re: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50
Still happens with Linux maryzen 6.8.0-136-generic #136~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 3 16:29:11 UTC x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2092703 Title: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu 22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2 with AMD Ryzen 5850U. As far as I noticed in boot logs from previous boot (journalctl -b -1), there is some problem with X.org: gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) FBDEV: driver for framebuffer: fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) VESA: driver for VESA chipsets: vesa gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for modesetting gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Unable to find a valid framebuffer device gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/fb0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: vesa: Ignoring device with a bound kernel driver gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "modesetting" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "fbdev" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "vesa" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Device(s) detected, but none match those in the config file. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Fatal server error: gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) no screens found(EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Please consult the The X.Org Foundation support gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: at http://wiki.x.org gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: for help. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Server terminated with error (1). Closing log file. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1664]: Unable to run X server gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: pam_unix(gdm-launch-environment:session): session closed for user gdm gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a kernel: logitech-hidpp-device 0003:046D:4082.0004: HID++ 4.5 device connected. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd[1]: session-c6.scope: Deactivated successfully. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: Child process -1664 was already dead. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Session c6 logged out. Waiting for processes to exit. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Removed session c6. When booting 6.8.0-49 (the one that works fine), I see it uses /dev/dri/card1 instead (extract from logs attached as kernel-6.8.0-49-journalctl-boot-logs-ok.txt). I'm also attaching: - cat /proc/version_signature > version.log (from the working kernel 6.8.0-49) - sudo lspci -vnvn > lspci-vnvn.log (from the working kernel 6.8.0-49) - apt-updated-packages.txt - a list of updated packages - kernel-6.8.0-50-journalctl-boot-logs-issue.txt - extract from logs from journalctl -b -1 (boot attempt using problematic kernel 6.8.0-50) - kernel-6.8.0-49-journalctl-boot-logs-ok.txt - extract from logs from journalctl -b -0 (booting working kernel 6.8.0-49) How can I make kernel 6.8.0-50 work? BR, Adrian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092703/+subscriptions
[Bug 2163121] Re: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28
** Description changed: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). - Fails in: Kernel 7.0.0-28 + Fails in: Kernel 7.0.0-28-generic Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: - Kernel: 7.0.0-14-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc - Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM - v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble + Kernel: 7.0.0-28-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc + Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM + v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: - Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 - Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 + Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 + Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: - Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled - arch: Zen 2 rev: 1 + Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled + arch: Zen 2 rev: 1 Graphics: - Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s - lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c - class-ID: 0300 + Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s + lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c + class-ID: 0300 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163121 Title: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28 Status in linux package in Ubuntu: New Bug description: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). Fails in: Kernel 7.0.0-28-generic Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: Kernel: 7.0.0-28-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163121/+subscriptions
[Bug 2131598] Re: Keyboard keys get stuck and repeat
Still happens with Linux maryzen 6.8.0-136-generic #136~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 3 16:29:11 UTC x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2131598 Title: Keyboard keys get stuck and repeat Status in linux package in Ubuntu: New Bug description: Once in a while, as I use my laptop (a Lenovo ThinkPad P16s Gen 2 AMD, running Ubuntu 22.04 and the proposed OEM kernel), as I am typing a key gets 'stuck', ie., it acts as if I never lifted the finger of the key. If I was typing an 'a' it starts writing 'aaaaaaaa' nonstop, if I was typing 'd' it will write 'dddddd', or, worse, if I was in vim an not in insert mode, it starts deleting all the file's lines, one by one. When this happens, nothing seems to make the input stop. It always happened to me while using vim inside a konsole. The only thing I have managed to do to make the input stop was to insert an USB keyboard on one of the USB slots - that made the input stop and the computer behave normally. After the fact I looked at dmesg but there was no indication whatsoever of something gone wrong. This happens to me infrequently (less than one per month), but it wasn't just once - and this can be perilous (in case the input being sent has a destructive action, like the 'delete' key on a file manager; or when there's no external keyboards around and the only choice is to force a shutdown by pressing the power key). Apparently I am not alone in this, for eg. you can see the same behavior on a Lenovo ThinkPad L14 Gen 2 running 20.04 reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/124406/comments/385 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131598/+subscriptions