** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
среда
[Bug 2149766] Re: Linux kernel 6.17.0-22.22 breaks amdxdna
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alice C. Munduruca (cremfuelled) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149766 Title: Linux kernel 6.17.0-22.22 breaks amdxdna Status in linux package in Ubuntu: New Status in linux-hwe-6.17 package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Bug description: The kernel update causes amdxdna to no longer load. [ 30.859857] amdxdna 0000:c7:00.1: [drm] *ERROR* amdxdna_drm_open: SVA bind device failed, ret -95 It works fine on 6.17.0-20. This is caused by this stable update: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142250 Specifically this commit: " iommu: disable SVA when CONFIG_X86 is set" It was also reported in 6.18.y upstream. https://lore.kernel.org/stable/870872aa-28e9-412a-bac6-8020bf560e4f@amd.com/ These commits are needed to fix it. commit 27bfafac65d8 ("mm: add a ptdesc flag to mark kernel page tables") commit 977870522af3 ("mm: actually mark kernel page table pages") commit 412d000346ea ("x86/mm: use 'ptdesc' when freeing PMD pages") commit 018942956723 ("mm: introduce pure page table freeing function") commit bf9e4e30f353 ("x86/mm: use pagetable_free()") commit 5ba2f0a15564 ("mm: introduce deferred freeing for kernel page tables") commit e37d5a2d60a3 ("iommu/sva: invalidate stale IOTLB entries for kernel address space") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149766/+subscriptions
[Bug 2077257] Re: dev-tpmrm0.device failed -> slow boot
** Tags added: systemd-boot ** Tags added: resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2077257 Title: dev-tpmrm0.device failed -> slow boot Status in linux package in Ubuntu: Confirmed Bug description: Hello, I tried the actual daily of Ubuntu 24.10. And the boot hang at job dev_tpm for 1:30min. sudo dmesg | grep tpm [ 1.193715] tpm_tis_remove+0xaa/0x100 [ 1.193719] tpm_tis_core_init+0x235/0x850 [ 1.193722] tpm_tis_init.part.0+0xc1/0x140 [ 1.193726] tpm_tis_plat_probe+0xc6/0x110 [ 1.194019] tpm_tis: probe of MSFT0101:00 failed with error -1 [ 3.906777] systemd[1]: Expecting device dev-tpmrm0.device - /dev/tpmrm0... This is the workaround: systemctl mask dev-tpmrm0.device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077257/+subscriptions
[Bug 2133180] Re: Bug Report Summary: HP OmniBook X 2-in-1 Accelerometer Missing (Intel Lunar Lake)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2133180 Title: Bug Report Summary: HP OmniBook X 2-in-1 Accelerometer Missing (Intel Lunar Lake) Status in linux package in Ubuntu: Confirmed Bug description: System Information: - OS: Ubuntu 25.10 - Kernel: 6.17.0-7-generic - Hardware: HP OmniBook X 2-in-1 (Intel Core Ultra 7 Lunar Lake) - ISH PCI Device: 00:12.0 Intel Corporation Lunar Lake-M Integrated Sensor Hub [8086:a845] (rev 10) Issue Description: The integrated accelerometer is not detected by the system, preventing auto-rotation. The Intel ISH (Integrated Sensor Hub) driver `intel_ish_ipc` is loaded, but it only detects the proximity sensor. Diagnostic Output: 1. Kernel Modules: `intel_ish_ipc` and `hid_sensor_hub` are loaded. `hid_sensor_prox` is loaded (Proximity sensor detected). `hid_sensor_accel_3d` or similar accelerometer modules are NOT loaded/used. 2. IIO Devices (`/sys/bus/iio/devices/`): Only `prox` devices are present. No `accel` devices found. 3. Modinfo `intel_ish_ipc`: Firmware `intel/ish/ish_lnlm.bin` is listed as available/supported by the module. Expected Behavior: The accelerometer should be exposed as an IIO device (e.g., `iio:deviceX` with name `accel_3d`) to allow `iio-sensor-proxy` to handle screen rotation. Suspected Cause: Missing or incorrect ISH firmware mapping for this specific HP Lunar Lake device in the Linux kernel or `linux-firmware` package. ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-7-generic 6.17.0-7.7 ProcVersionSignature: Ubuntu 6.17.0-7.7-generic 6.17.2 Uname: Linux 6.17.0-7-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: cedric 9710 F.... pipewire cedric 9729 F.... wireplumber /dev/snd/seq: cedric 9710 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 27 20:23:18 2025 InstallationDate: Installed on 2025-11-19 (8 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: HP HP OmniBook X Flip Laptop 14-fm0xxx ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-7-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2025 dmi.bios.release: 15.7 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8D9F dmi.board.vendor: HP dmi.board.version: 46.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 46.32 dmi.modalias: dmi:bvnInsyde:bvrF.07:bd06/24/2025:br15.7:efr46.32:svnHP:pnHPOmniBookXFlipLaptop14-fm0xxx:pvrType1ProductConfigId:rvnHP:rn8D9F:rvr46.32:cvnHP:ct31:cvrChassisVersion:skuC92QREA#UUZ: dmi.product.family: 103C_5335M8 HP OmniBook X dmi.product.name: HP OmniBook X Flip Laptop 14-fm0xxx dmi.product.sku: C92QREA#UUZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2133180/+subscriptions
[Bug 2146391] Re: [resolute] Can't suspend
Paride pointed me at https://github.com/canonical/lxd/issues/17983 and that seems to be my case as well. I stopped the running lxd container, and then suspend worked just fine. ** Bug watch added: LXD bug tracker #17983 https://github.com/canonical/lxd/issues/17983 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2146391 Title: [resolute] Can't suspend Status in linux package in Ubuntu: New Bug description: There is no "suspend" option in the power menu on the top right, and when I run `sudo systemctl suspend -i`, I see the kernel complaining in dmesg: [Wed Mar 25 20:18:48 2026] Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0): And the laptop does not suspend. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-10-generic 7.0.0-10.10 ProcVersionSignature: Ubuntu 7.0.0-10.10-generic 7.0.0-rc4 Uname: Linux 7.0.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.33.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: andreas 5136 F.... wireplumber /dev/snd/seq: andreas 5116 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 20:20:17 2026 InstallationDate: Installed on 2025-09-18 (188 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Beta amd64 (20250917.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: LENOVO 20HRCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-10-generic root=/dev/mapper/vg0-root ro intel_iommu=on i915.enable_gvt=1 quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-23 (2 days ago) dmi.bios.date: 02/15/2024 dmi.bios.release: 1.62 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET77W (1.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN1MET77W(1.62):bd02/15/2024:br1.62:efr1.22:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HR_BU_Think_FM_ThinkPadX1Carbon5th:pfaThinkPadX1Carbon5th: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146391/+subscriptions
[Bug 1982483]
(In reply to Zhang Heng from comment #48) > (In reply to Rudolf from comment #46) > > > Sorry, but that suggestion won't work. The kernel expects a predefined > model > > name at that point, such as hp-aio or dell-headset-multi. The kernel > doesn't > > recognize model=103c:885e and will ignore it. Only a clean kernel patch > will > > work. In my opinion. > > 885e is your codec ssid, which is currently the sound card that needs to be > resolved but has not been resolved. What I wrote is that 86c7 corresponds to > another repair solution that already exists in the kernel, similar to a > model approach. Ok, thanks, I got it and I'll try it. But it might take a while. My "fix" works perfectly at the moment ;-). -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci0000:00/0000:00:1f.3 SysFS BusID: 0000:00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x6105000000-0x61050fffff (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v00008086d00007AD0sv0000103Csd000089E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[ 3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[ 3.582359] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[ 3.582362] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[ 3.582364] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 <6>[ 3.582366] snd_hda_codec_realtek hdaudioC0D0: inputs: <6>[ 3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[ 3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F.... pulseaudio /dev/snd/controlC0: ernst 1560 F.... pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions
[Bug 2149806] Re: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph
** Description changed: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. - The IPU6 stack loads, userspace components work, and a loopback camera - device is created, but the physical camera sensor never appears in the - media graph. The key kernel error is: + ## System info + - **Laptop**: Huawei MateBook X Pro 2024 + - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) + - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) + - **Kernels tested**: + - `6.17.0-22-generic` + - `6.17.0-1017-oem` + The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never + appears in the media graph. + + The key kernel error is: + + ```text int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - This reproduces on both: - - - 6.17.0-22-generic - - 6.17.0-1017-oem - - ## System - - - Laptop: Huawei MateBook X Pro 2024 - - CPU: Intel Core Ultra 7 155H - - OS: Zorin OS 18.1 Pro (Ubuntu 24.04 based) - - ## What works + ## What works The following components are installed and functional: - gstreamer1.0-icamera - libcamhal-ipu6epmtl - v4l2-relayd - IPU6 kernel modules A userspace-facing virtual camera is created as: - Intel MIPI Camera on /dev/video0 - gst-inspect-1.0 icamerasrc succeeds. + Also: - ## What fails + - gst-inspect-1.0 icamerasrc succeeds + + ## What fails The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - Intel IPU6 CSI2 0..5 - Intel IPU6 ISYS Capture 0..47 appear. No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). As a result, /dev/video0 exists but only outputs black frames. - ## dmesg + ## dmesg int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE intel-ipu6 0000:00:05.0: CSE authenticate_run done intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 - ## media-ctl observation + ## Possible sensor information from ACPI tables + + I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure + happens before sensor probe completes. + + However, scanning the ACPI tables shows that the firmware contains + references to multiple OmniVision sensor IDs, including: + + - OVTI01AS + - OVTI01A0 + - OVTI13B1 + + and also camera-related strings such as: + + - CAM0 + - CAM1 + - CAMERA_V1P8S1 + - CAMERA_V3P3S1 + + So the system firmware appears to describe at least one OmniVision-based camera path, but the exact sensor model cannot currently be + confirmed from Linux. + + ## media-ctl observation media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. - ## Additional notes + ## Conclusion - I also tested the OEM kernel (6.17.0-1017-oem) and the failure is - unchanged, including the same INT3472:02 GPIO error. - - This looks like a platform-specific INT3472 / GPIO / ACPI issue - preventing the camera sensor from being initialized. + This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the + camera sensor from being initialized. ** Description changed: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. - ## System info - - **Laptop**: Huawei MateBook X Pro 2024 - - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) - - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) - - **Kernels tested**: - - `6.17.0-22-generic` - - `6.17.0-1017-oem` + ## System info + - **Laptop**: Huawei MateBook X Pro 2024 + - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) + - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) + - **Kernels tested**: + - `6.17.0-22-generic` + - `6.17.0-1017-oem` - The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never - appears in the media graph. + The IPU6 stack loads, userspace components work, and a loopback camera + device is created, but the physical camera sensor never appears in the + media graph. - The key kernel error is: + The key kernel error is: - ```text - int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO - int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 + int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO + int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - ## What works + ## What works - The following components are installed and functional: + The following components are installed and functional: - - gstreamer1.0-icamera - - libcamhal-ipu6epmtl - - v4l2-relayd - - IPU6 kernel modules + - gstreamer1.0-icamera + - libcamhal-ipu6epmtl + - v4l2-relayd + - IPU6 kernel modules - A userspace-facing virtual camera is created as: + A userspace-facing virtual camera is created as: - - Intel MIPI Camera on /dev/video0 + - Intel MIPI Camera on /dev/video0 - Also: + Also: - - gst-inspect-1.0 icamerasrc succeeds + - gst-inspect-1.0 icamerasrc succeeds - ## What fails + ## What fails - The integrated sensor is never brought up. In media-ctl -p -d + The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - - Intel IPU6 CSI2 0..5 - - Intel IPU6 ISYS Capture 0..47 + - Intel IPU6 CSI2 0..5 + - Intel IPU6 ISYS Capture 0..47 - appear. + appear. - No actual sensor entity appears (for example no ov01a10, ov01a1s, + No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). - As a result, /dev/video0 exists but only outputs black frames. + As a result, /dev/video0 exists but only outputs black frames. - ## dmesg + ## dmesg - int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO - int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE - intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE - intel-ipu6 0000:00:05.0: CSE authenticate_run done - intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 + int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO + int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 + intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE + intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE + intel-ipu6 0000:00:05.0: CSE authenticate_run done + intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 - ## Possible sensor information from ACPI tables + ## Possible sensor information from ACPI tables - I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure - happens before sensor probe completes. + I still cannot identify the physically probed sensor with certainty, + because no sensor entity appears in media-ctl and the failure happens + before sensor probe completes. - However, scanning the ACPI tables shows that the firmware contains + However, scanning the ACPI tables shows that the firmware contains references to multiple OmniVision sensor IDs, including: - - OVTI01AS - - OVTI01A0 - - OVTI13B1 + - OVTI01AS + - OVTI01A0 + - OVTI13B1 - and also camera-related strings such as: + and also camera-related strings such as: - - CAM0 - - CAM1 - - CAMERA_V1P8S1 - - CAMERA_V3P3S1 + - CAM0 + - CAM1 + - CAMERA_V1P8S1 + - CAMERA_V3P3S1 - So the system firmware appears to describe at least one OmniVision-based camera path, but the exact sensor model cannot currently be - confirmed from Linux. + So the system firmware appears to describe at least one OmniVision-based + camera path, but the exact sensor model cannot currently be confirmed + from Linux. - ## media-ctl observation + ## media-ctl observation - media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, + media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. - ## Conclusion + ## Conclusion - This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the - camera sensor from being initialized. + This reproduces unchanged on both tested kernels and looks like a + platform-specific INT3472 / GPIO / ACPI issue preventing the camera + sensor from being initialized. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149806 Title: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph Status in linux package in Ubuntu: New Bug description: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. ## System info - **Laptop**: Huawei MateBook X Pro 2024 - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) - **Kernels tested**: - `6.17.0-22-generic` - `6.17.0-1017-oem` The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never appears in the media graph. The key kernel error is: int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 ## What works The following components are installed and functional: - gstreamer1.0-icamera - libcamhal-ipu6epmtl - v4l2-relayd - IPU6 kernel modules A userspace-facing virtual camera is created as: - Intel MIPI Camera on /dev/video0 Also: - gst-inspect-1.0 icamerasrc succeeds ## What fails The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - Intel IPU6 CSI2 0..5 - Intel IPU6 ISYS Capture 0..47 appear. No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). As a result, /dev/video0 exists but only outputs black frames. ## dmesg int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE intel-ipu6 0000:00:05.0: CSE authenticate_run done intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 ## Possible sensor information from ACPI tables I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure happens before sensor probe completes. However, scanning the ACPI tables shows that the firmware contains references to multiple OmniVision sensor IDs, including: - OVTI01AS - OVTI01A0 - OVTI13B1 and also camera-related strings such as: - CAM0 - CAM1 - CAMERA_V1P8S1 - CAMERA_V3P3S1 So the system firmware appears to describe at least one OmniVision- based camera path, but the exact sensor model cannot currently be confirmed from Linux. ## media-ctl observation media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. ## Conclusion This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the camera sensor from being initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149806/+subscriptions
[Bug 2148761] Re: xhci_hcd "Controller not ready at resume -19" hard system hang on Zen 4 (Raphael) — runtime PM resume failure on 12:00.x PCIe complex
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148761 Title: xhci_hcd "Controller not ready at resume -19" hard system hang on Zen 4 (Raphael) — runtime PM resume failure on 12:00.x PCIe complex Status in linux package in Ubuntu: New Bug description: ## System - Ubuntu 24.04 - Kernel: first known broken 6.8.0-106-generic (large update in early March 2026 skipped several versions; last known good version unknown) - CPU: AMD Ryzen 9 7950X3D (Zen 4, Raphael) - GPU: NVIDIA RTX 4090 (primary), AMD Raphael integrated GPU present (0000:12:00.0, device 0x164e) but not used for display - Motherboard: ASUS TUF GAMING X670E-PLUS WIFI - Xorg (not Wayland) ## Symptom Hard system hang — instant black screen, no kernel panic, no OOPS, machine reboots as if reset button was pressed. No kernel log output from the crash itself. Timing is random — anywhere from under a minute to several hours after trigger. Machine can crash after the triggering application has already exited. ## Dmesg evidence (captured via remote dmesg streaming) Last kernel messages before every hang are consistently: xhci_hcd 0000:12:00.3: Controller not ready at resume -19 xhci_hcd 0000:12:00.3: PCI post-resume error -19! xhci_hcd 0000:12:00.3: HC died; cleaning up or the same sequence on 0000:12:00.4. Both are USB controllers that are functions of the Raphael APU PCIe device (0000:12:00.x complex, which also includes the iGPU, HD audio, and PSP/crypto engine). At time of crash, these controllers show: power/control: auto runtime_enabled: enabled runtime_status: suspended runtime_suspended_time: ~657000ms (suspended for almost entire uptime) ## Trigger In this case the crash was consistently triggered by running WiVRn OpenXR server (https://github.com/WiVRn/WiVRn), which is a long-running Vulkan application. However WiVRn is likely just making the crash happen faster — see similar report below with no VR software involved at all. Note: crash timing is non-deterministic. It can occur while WiVRn is running, after WiVRn has exited, and even with no Quest headset connected. General desktop use alone is sufficient to eventually trigger it per the similar report below. ## Similar report Identical dmesg signature reported on Fedora 43 (December 2025) on a pure AMD system (Ryzen 7 9700X + RX 9070 XT) with no VR software, triggered by general desktop use: https://discussion.fedoraproject.org/t/constant-random-crashing-unable-to-identify-cause/177192 This suggests the bug is not specific to NVIDIA+AMD configurations, not specific to VR software, and is likely an upstream kernel regression affecting Zen 4 systems broadly. ## Workaround Preventing runtime PM suspend of the Raphael PCIe complex: for dev in /sys/bus/pci/devices/0000:12:00.{1,3,4,6}/power/control; do echo on | sudo tee $dev done This appears stable across extended sessions. Note: addresses symptom only, does not fix the underlying resume failure. The Fedora user resolved it with kernel boot parameters: pcie_port_pm=off usbcore.autosuspend=-1 iommu=pt (broader in scope — disables PCIe port PM and USB autosuspend globally) ## What is NOT known - Exactly which kernel version introduced the regression (skipped several versions in a large update) - Whether WiVRn/Vulkan/amdgpu initialization of the iGPU plays any role in triggering the PM instability, or whether it would crash eventually from general desktop use alone (not yet tested) - Which of the three Fedora boot parameters is actually necessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148761/+subscriptions
[Bug 2149806] Re: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149806 Title: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph Status in linux package in Ubuntu: New Bug description: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. ## System info - **Laptop**: Huawei MateBook X Pro 2024 - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) - **Kernels tested**: - `6.17.0-22-generic` - `6.17.0-1017-oem` The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never appears in the media graph. The key kernel error is: int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 ## What works The following components are installed and functional: - gstreamer1.0-icamera - libcamhal-ipu6epmtl - v4l2-relayd - IPU6 kernel modules A userspace-facing virtual camera is created as: - Intel MIPI Camera on /dev/video0 Also: - gst-inspect-1.0 icamerasrc succeeds ## What fails The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - Intel IPU6 CSI2 0..5 - Intel IPU6 ISYS Capture 0..47 appear. No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). As a result, /dev/video0 exists but only outputs black frames. ## dmesg int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE intel-ipu6 0000:00:05.0: CSE authenticate_run done intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 ## Possible sensor information from ACPI tables I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure happens before sensor probe completes. However, scanning the ACPI tables shows that the firmware contains references to multiple OmniVision sensor IDs, including: - OVTI01AS - OVTI01A0 - OVTI13B1 and also camera-related strings such as: - CAM0 - CAM1 - CAMERA_V1P8S1 - CAMERA_V3P3S1 So the system firmware appears to describe at least one OmniVision- based camera path, but the exact sensor model cannot currently be confirmed from Linux. ## media-ctl observation media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. ## Conclusion This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the camera sensor from being initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149806/+subscriptions
[Bug 2100828] Re: ubuntu-24.04: Root port link speed degradation to 2.5GT/s after nvme hot plug
Hi Tim, Thank you for providing the test kernel. We have completed the verification, and this test kernel has been confirmed to resolve the issue. Best Regards, Ziyou -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2100828 Title: ubuntu-24.04: Root port link speed degradation to 2.5GT/s after nvme hot plug Status in linux package in Ubuntu: Triaged Bug description: We found a kenrel issue on Redhat 9.4 and 9.5. nvme pcie link speed will downgrade to 2.5GT/s after hotplug. After analysis, we found this patch casued this issue: a89c82249c37 ("PCI: Work around PCIe link training failures"). This patch also merged into ubuntu 24.04, therefore, this issue will also occur on 24.04. The following commits fix this issue: commit de9a6c8d5dbfedb5eb3722c822da0490f6a59a45 PCI/bwctrl: Add pcie_set_target_speed() to set PCIe Link Speed f68dea13405c94381d08f42dbf0416261622bdad ("PCI: Revert to the original speed after PCIe failed link") Could you help check whetehr ubuntu need add the fix patch on 24.04 version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100828/+subscriptions
вторник
[Bug 2149792] [NEW] games stuttering/freezing in kernel 7.0.0-14
Public bug reported: I play Call of Duty Black Ops 2 Zombies on steam using default proton settings. No special proton settings. I play Far Cry 3 on steam with the glorious eggroll custom proton. Using kernel 7.0.0-14 Zombies gives me a brief freeze frame almost like somebody hit a pause button that is making it hard to play. Using kernel 7.0.0-14 Far Cry 3 occasionally gives me audio that sounds like a cd player skipping or something. If I run zombies in window mode, and btop running next to it, I can observe that the freeze corresponds to a drop in CPU usage. Some times it goes from maybe 20 percent and then freezes and drops to 2 percent. If I enable "X3D turbo mode" in my computer bios the freeze seems to go away, but I only have 8 CPUS now. If I go back to kernel 7.0.0-13, the freeze problem also goes away. This makes me think its a bug in the kernel but I don't know it could be a bug in something else. Sorry I have never debugged a linux kernel before. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: ryan 4501 F.... wireplumber /dev/snd/controlC1: ryan 4501 F.... wireplumber /dev/snd/controlC0: ryan 4501 F.... wireplumber /dev/snd/seq: ryan 4417 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 06:44:25 2026 InstallationDate: Installed on 2026-03-30 (22 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) IwDevWlp15s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X870E AORUS PRO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F12a dmi.board.asset.tag: Default string dmi.board.name: X870E AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF12a:bd03/11/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnX870EAORUSPRO:pvrDefaultstring-CF-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnX870EAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX870EMB: dmi.product.family: X870E MB dmi.product.name: X870E AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string-CF-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149792 Title: games stuttering/freezing in kernel 7.0.0-14 Status in linux package in Ubuntu: New Bug description: I play Call of Duty Black Ops 2 Zombies on steam using default proton settings. No special proton settings. I play Far Cry 3 on steam with the glorious eggroll custom proton. Using kernel 7.0.0-14 Zombies gives me a brief freeze frame almost like somebody hit a pause button that is making it hard to play. Using kernel 7.0.0-14 Far Cry 3 occasionally gives me audio that sounds like a cd player skipping or something. If I run zombies in window mode, and btop running next to it, I can observe that the freeze corresponds to a drop in CPU usage. Some times it goes from maybe 20 percent and then freezes and drops to 2 percent. If I enable "X3D turbo mode" in my computer bios the freeze seems to go away, but I only have 8 CPUS now. If I go back to kernel 7.0.0-13, the freeze problem also goes away. This makes me think its a bug in the kernel but I don't know it could be a bug in something else. Sorry I have never debugged a linux kernel before. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: ryan 4501 F.... wireplumber /dev/snd/controlC1: ryan 4501 F.... wireplumber /dev/snd/controlC0: ryan 4501 F.... wireplumber /dev/snd/seq: ryan 4417 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 06:44:25 2026 InstallationDate: Installed on 2026-03-30 (22 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) IwDevWlp15s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X870E AORUS PRO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F12a dmi.board.asset.tag: Default string dmi.board.name: X870E AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF12a:bd03/11/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnX870EAORUSPRO:pvrDefaultstring-CF-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnX870EAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX870EMB: dmi.product.family: X870E MB dmi.product.name: X870E AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string-CF-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149792/+subscriptions
[Bug 2149808] Re: Qualcomm X1E: Speaker overdrive causes hardware protection shutdown
** Description changed: + [ Impact ] + On Qualcomm X1 SoCs the Linux upstream audio support is currently lacking active speaker protection support in the DSP or software. Since 26.04. all the upstream changes have landed to enable audio/speakers by default on some devices using this SoC (Thinkpad T14s). Unfortunately the current default does not seem to be safe to use. Playing music and turning the speaker up to 100% causes a hardware safety mechanism to trigger and shut down the speakers entirely until the next reboot. Such a safety mechanism is not guaranteed and on some devices the impact might even be worse. The previous SoC generation fixed this by limiting the volume in the Linux kernel driver, see https://github.com/torvalds/linux/commit/c481016bb4f8a9c059c39ac06e7b65e233a61f6a I believe the same should be done for the X1 family. A patch to do that is available on the linux-arm-msm mailing list https://patchwork.kernel.org/project/linux-arm- msm/patch/20260421-x1e80100-audio-limit-v1-1-98bac8cee2ee@canonical.com/ + + [ Test Plan ] + + The bug is trivial to reproduce (buy I don't recommend trying if you + value your hardware) by playing audio and slowly increasing the system + volume until the speakers stop working. + + With the fix applied, it should be possible to go to 100% volume without + breaking the speakers. + + [ Where problems could occur ] + + This only affects machines based on this specific soc, of which only few + have firmware and alsa config upstream to work out of the box. On those + devices there is a small risk that our patch could break something in + the audio driver but the impact would be low and broken audio is not a + major regression since this is the first release where it would work out + the box. ** Also affects: linux (Ubuntu Resolute) 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/2149808 Title: Qualcomm X1E: Speaker overdrive causes hardware protection shutdown Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: [ Impact ] On Qualcomm X1 SoCs the Linux upstream audio support is currently lacking active speaker protection support in the DSP or software. Since 26.04. all the upstream changes have landed to enable audio/speakers by default on some devices using this SoC (Thinkpad T14s). Unfortunately the current default does not seem to be safe to use. Playing music and turning the speaker up to 100% causes a hardware safety mechanism to trigger and shut down the speakers entirely until the next reboot. Such a safety mechanism is not guaranteed and on some devices the impact might even be worse. The previous SoC generation fixed this by limiting the volume in the Linux kernel driver, see https://github.com/torvalds/linux/commit/c481016bb4f8a9c059c39ac06e7b65e233a61f6a I believe the same should be done for the X1 family. A patch to do that is available on the linux-arm-msm mailing list https://patchwork.kernel.org/project/linux-arm- msm/patch/20260421-x1e80100-audio- limit-v1-1-98bac8cee2ee@canonical.com/ [ Test Plan ] The bug is trivial to reproduce (buy I don't recommend trying if you value your hardware) by playing audio and slowly increasing the system volume until the speakers stop working. With the fix applied, it should be possible to go to 100% volume without breaking the speakers. [ Where problems could occur ] This only affects machines based on this specific soc, of which only few have firmware and alsa config upstream to work out of the box. On those devices there is a small risk that our patch could break something in the audio driver but the impact would be low and broken audio is not a major regression since this is the first release where it would work out the box. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149808/+subscriptions
[Bug 2149792] Re: games stuttering/freezing in kernel 7.0.0-14
** Description changed: I play Call of Duty Black Ops 2 Zombies on steam using default proton settings. No special proton settings. I play Far Cry 3 on steam with the glorious eggroll custom proton. Using kernel 7.0.0-14 Zombies gives me a brief freeze frame almost like somebody hit a pause button that is making it hard to play. Using kernel 7.0.0-14 Far Cry 3 occasionally gives me audio that sounds like a cd player skipping or something. If I run zombies in window mode, and btop running next to it, I can observe that the freeze corresponds to a drop in CPU usage. Some times it goes from maybe 20 percent and then freezes and drops to 2 percent. If I enable "X3D turbo mode" in my computer bios the freeze seems to go away, but I only have 8 CPUS now. If I go back to kernel 7.0.0-13, the freeze problem also goes away. This makes me think its a bug in the kernel but I don't know it could be a bug in something else. Sorry I have never debugged a linux kernel before. - I realize my open source friends maybe don't have those steam games to - test. So I decided to try SuperTuxKart. + I realize my friends maybe don't have those steam games to test. So I + decided to try SuperTuxKart. sudo apt install supertuxkart Sure enough after playing for a bit, I got a stutter where the CPU usage dropped. That game doesn't use very much CPU power so it dropped from like 0.2 percent to 0.0 percent. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: ryan 4501 F.... wireplumber /dev/snd/controlC1: ryan 4501 F.... wireplumber /dev/snd/controlC0: ryan 4501 F.... wireplumber /dev/snd/seq: ryan 4417 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 06:44:25 2026 InstallationDate: Installed on 2026-03-30 (22 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) IwDevWlp15s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X870E AORUS PRO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F12a dmi.board.asset.tag: Default string dmi.board.name: X870E AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF12a:bd03/11/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnX870EAORUSPRO:pvrDefaultstring-CF-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnX870EAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX870EMB: dmi.product.family: X870E MB dmi.product.name: X870E AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string-CF-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149792 Title: games stuttering/freezing in kernel 7.0.0-14 Status in linux package in Ubuntu: New Bug description: I play Call of Duty Black Ops 2 Zombies on steam using default proton settings. No special proton settings. I play Far Cry 3 on steam with the glorious eggroll custom proton. Using kernel 7.0.0-14 Zombies gives me a brief freeze frame almost like somebody hit a pause button that is making it hard to play. Using kernel 7.0.0-14 Far Cry 3 occasionally gives me audio that sounds like a cd player skipping or something. If I run zombies in window mode, and btop running next to it, I can observe that the freeze corresponds to a drop in CPU usage. Some times it goes from maybe 20 percent and then freezes and drops to 2 percent. If I enable "X3D turbo mode" in my computer bios the freeze seems to go away, but I only have 8 CPUS now. If I go back to kernel 7.0.0-13, the freeze problem also goes away. This makes me think its a bug in the kernel but I don't know it could be a bug in something else. Sorry I have never debugged a linux kernel before. I realize my friends maybe don't have those steam games to test. So I decided to try SuperTuxKart. sudo apt install supertuxkart Sure enough after playing for a bit, I got a stutter where the CPU usage dropped. That game doesn't use very much CPU power so it dropped from like 0.2 percent to 0.0 percent. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: ryan 4501 F.... wireplumber /dev/snd/controlC1: ryan 4501 F.... wireplumber /dev/snd/controlC0: ryan 4501 F.... wireplumber /dev/snd/seq: ryan 4417 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 06:44:25 2026 InstallationDate: Installed on 2026-03-30 (22 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) IwDevWlp15s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X870E AORUS PRO ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F12a dmi.board.asset.tag: Default string dmi.board.name: X870E AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF12a:bd03/11/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnX870EAORUSPRO:pvrDefaultstring-CF-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnX870EAORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX870EMB: dmi.product.family: X870E MB dmi.product.name: X870E AORUS PRO dmi.product.sku: Default string dmi.product.version: Default string-CF-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149792/+subscriptions