[Bug 2174540] Re: Kernel regression hangs suspend and shutdown on Dell Precision 3510

** 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/2174540 Title: Kernel regression hangs suspend and shutdown on Dell Precision 3510 Status in linux package in Ubuntu: New Bug description: Here is a concise bug description structured directly according to the Ubuntu bug reporting guidelines shown in the image: 1. Ubuntu release: > lsb_release -rd Description: Ubuntu 24.04.5 LTS Release: 24.04 2. Package version: `linux-image-7.0.0-43-generic` (kernel regression introduced compared to working version `7.0.0-42-generic`) 3. What you expected to happen: The laptop should successfully enter suspend mode (turning off the display and sleeping cleanly) and power down completely during a system shutdown. 4. What happened instead: Upon initiating suspend or shutdown, the screen goes black while hardware sound loops or persists indefinitely, hanging the system and requiring a hard power-off via the power button on a Dell Precision 3510 (Intel HD Graphics 530). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43~24.04.1 ProcVersionSignature: Ubuntu 7.0.0-43.43~24.04.1-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: mahdi 2383 F.... wireplumber /dev/snd/seq: mahdi 2379 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 20:05:47 2026 InstallationDate: Installed on 2025-03-08 (617 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: Dell Inc. Precision 3510 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=7d4d5537-a4c2-45e1-bb59-511fd8b10d17 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-7.0.0-43-generic N/A linux-backports-modules-7.0.0-43-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux-hwe-7.0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.34 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.34.3 dmi.board.name: 0PVGJH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.34.3:bd11/20/2022:br1.34:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0PVGJH:rvrA00:cvnDellInc.:ct9:cvr:sku06E0:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3510 dmi.product.sku: 06E0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174540/+subscriptions

[Bug 2174545] Re: MT7601U (148f:7601) fails during RXIQ calibration on Ubuntu kernel 7.0.0-43-generic; experimental bypass restores Wi-Fi

** 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/2174545 Title: MT7601U (148f:7601) fails during RXIQ calibration on Ubuntu kernel 7.0.0-43-generic; experimental bypass restores Wi-Fi Status in linux package in Ubuntu: New Bug description: A USB Wi-Fi adapter using the MediaTek/Ralink MT7601U chipset (USB ID 148f:7601) fails to initialize reliably with Ubuntu's stock mt7601u kernel driver. Detailed instrumentation of the driver identified repeated timeouts during RXIQ calibration. An experimental modification that skips only RXIQ calibration allows the adapter to initialize and operate successfully. Environment Distribution: Ubuntu 26.04.1 LTS Kernel: 7.0.0-43-generic USB device: 148f:7601 Kernel module: mt7601u Wireless interface: wlx00e0467e27e0 Observed failure With the stock driver: Adapter initialization fails or becomes unreliable. RXIQ calibration repeatedly returns -110 (timeout). USB communication errors with status -71 have also been observed. The wireless interface cannot be used reliably. Instrumented driver logs locate the initialization failure at the RXIQ calibration stage, after TXIQ and before DPD. Experimental workaround A modified driver introduces the module parameter: skip_rxiq=1 The modification bypasses the RXIQ calibration invocation while retaining other calibration stages, including DPD. The driver also contains an optional vnd_reset diagnostic parameter, disabled during successful testing. Validation results Using the modified driver: Device initializes and registers a wireless interface. Wi-Fi scanning succeeds. WPA2 authentication succeeds. DHCP configuration succeeds. Internet connectivity works. Automatic reconnection after reboot succeeds. Wi-Fi-only networking and remote SSH access succeed. A 15-minute ICMP test completed with 447/450 responses (0.67% packet loss). No new MT7601U communication errors were observed during the final stability check. Expected behavior The stock mt7601u driver should initialize the device, complete or safely handle radio calibration, and provide functional Wi-Fi connectivity without a locally modified kernel module. Actual behavior RXIQ calibration times out and device initialization fails. Bypassing RXIQ allows successful operation. Request Please investigate the RXIQ calibration timeout and USB error handling in the mt7601u driver. In particular, determine whether RXIQ calibration requires corrected timing, command handling, firmware interaction, or a hardware-specific fallback. The RXIQ bypass is an experimental diagnostic workaround, not a validated upstream fix. I can provide the modified driver source, calibration-stage instrumentation, original failure logs and successful test results for review. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174545/+subscriptions

[Bug 2174549] Re: Razer Blade 2019 (i7-8750H/UHD 630/144 Hz eDP): hard freeze with last frame retained; stable with i915.enable_psr=0 + intel_idle.max_cstate=4

** 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/2174549 Title: Razer Blade 2019 (i7-8750H/UHD 630/144 Hz eDP): hard freeze with last frame retained; stable with i915.enable_psr=0 + intel_idle.max_cstate=4 Status in linux package in Ubuntu: New Bug description: # Summary Ubuntu 26.04.1 on a Razer Blade 2019 (RZ09-02386G91) hard-freezes: the internal eDP panel keeps the last frame, keyboard/touchpad and the Caps Lock LED stop responding, and the machine must be powered off. There is no panic, oops, MCE/EDAC, Xid/NVRM, thermal event, NVMe timeout/reset, or ext4 error; the journal simply ends. First observed in August 2026 with Ubuntu 26.04. With default power management (i915 PSR auto, intel_idle default C-states), freezes occurred after ~1-2 h of idle or light browsing. The combination `i915.enable_psr=0 intel_idle.max_cstate=4` has now survived ~82 h over 9 boots, including AC and battery, idle and load, Wi-Fi, touchpad, GPU, and suspend/resume. Each parameter alone has failed or was tested with a confounder, so I cannot yet attribute the bug to a single subsystem. # Hardware / software - Razer Blade 2019 RZ09-02386G91, BIOS 1.08 (2019-05-21), ME 12.0.81.1753 - Intel Core i7-8750H (Coffee Lake-H, 6C/12T) - Intel UHD Graphics 630 [8086:3e9b], i915 - NVIDIA GTX 1070 Mobile, nvidia 580.178.04, PRIME on-demand; no Xid, dGPU idle in P8; internal panel driven by i915 - 2x8 GB DDR4-2667, non-ECC; memtest86+ 8.00, 5 passes, 0 errors - Samsung PM981 256 GB (MZVLB256HAHQ-00000, FW EXD7101Q); also reproduced with a Kingston NV3 1 TB - Intel Wireless-AC 9260; internal eDP 1920x1080@144 Hz (LGD 05C0), PSR1 supported - Ubuntu 26.04.1 LTS, kernel 7.0.0-42-generic, GNOME 50.1/Wayland, systemd 259.9 - Secure Boot enabled; freezes also occurred with Secure Boot disabled # Symptom - The display keeps the last frame and does not update. - Keyboard, touchpad and Caps Lock LED do not respond; forced power-off is required. - No panic/oops/MCE/EDAC/Xid/NVRM/thermal/NVMe/ext4 message; the journal ends abruptly. - No pstore/kdump record was captured. - Reproduced on two different SSDs and after a clean reinstall, so the SSD is not the common cause. # Tests and observations | Configuration | Result | |---|---| | Default: PSR auto, C-states auto | Freeze after ~1-2 h (historical; first seen Aug 2026) | | 2026-11-03 10:59, PSR auto, after fwupd commands | Freeze; no logs. fwupd later ruled out with 6 repetitions | | 2026-11-04 10:17, `i915.enable_psr=0` only | Freeze in idle; PSR disabled, DC5=0 | | 2026-11-04 12:18, `intel_idle.max_cstate=4` only, PSR auto | Freeze while browsing; DC5=790. C-state test contaminated by PSR auto | | 2026-11-04 to 2026-11-11, `i915.enable_psr=0 intel_idle.max_cstate=4` | ~82 h uptime over 9 boots, no freeze; AC and battery, idle/load, Wi-Fi, touchpad, GPU, suspend/resume | i915 observations: - PSR1 is supported by the panel and PSR was enabled by default. - With PSR auto, `i915_dmc_info` shows DC5 entry/exit churn (~1/s); DC6=0. With PSR=0, PSR mode is disabled and the churn stops, but DC5 still increments on blank/suspend (e.g. 428 after 8 h 48 min, 917 after 10 h 57 min); DC6=0. - Package C-states: default C10 is the dominant core idle state, but package C10=0; package C7 was observed. With `max_cstate=4`, C6 is the maximum and package C7=0. - No GPU hang, no i915 error capture, no `Atomic update failure` or `flip_done` messages in the freezing boots. # What was ruled out / confounders - RAM: memtest86+ 8.00, 5 passes, 0 errors. - SSD: reproduced with two different SSDs; PM981 SMART has 0 media errors; 55 unsafe shutdowns correspond to forced power-offs; ~12.5k error-log entries are benign `Invalid Field in Command` probes from smartd. - fwupd/Secure Boot: 6 fwupd repetitions, no freeze; freezes continued with Secure Boot off. - Thermal: no throttling; package ~51-62 C in normal use; memtest 75-79 C. - NVIDIA: no Xid/NVRM; dGPU idle in P8; internal panel on i915. A blacklist test is planned only if needed. - NVMe/PCIe: no timeouts/resets; AER is not supported by the platform, so PCIe errors would be invisible; ASPM/APST remains a secondary hypothesis. # Request Is this a known i915 PSR/DC5 vs package C-state interaction on Coffee Lake-H? Is there a quirk or fix I should test? I can run a single-variable test with `i915.enable_dc=0` next (as in the similar HP EliteDesk 800 G4 report), or test a mainline/drm-tip kernel if you prefer. I can also enable pstore/NMI watchdog to try to capture the next hard lockup. # Related reports - Launchpad #2172666 — HP 250 G9, Alder Lake, 26.04.1: hard freeze in idle; journal cut; stable with `pcie_aspm=off intel_idle.max_cstate=3 nvme_core.default_ps_max_latency_us=5500 i915.enable_psr=0`. - Launchpad #2169758 — Lenovo IdeaPad 320, UHD 620, 24.04 HWE 7.0.0-38: hard freeze preceded by `Atomic update failure on pipe A`. - Launchpad #2172032 — ASUS VivoBook X513EQ, Tiger Lake i915 + NVIDIA 580.178.04: hard freeze at login; `nomodeset` works. - i915 GitLab #17758 — Haswell, `Atomic update failure on pipe A`, freezes on Wayland; `i915.enable_psr=0` helps. - i915 GitLab #4813 — Dell Latitude 7390: freeze with PSR active; `enable_psr=0` workaround. - i915 GitLab #13835 — HP ProOne 600, CFL UHD 630: DPMS standby/powerdown crash without logs. - Ubuntu Discourse — HP EliteDesk 800 G4 Mini, i5-8500T, UHD 630, 26.04.1: hard freezes; ~170 h stable with `i915.enable_dc=0`. # Attachments - `journalctl -b -1` for the two freezing boots (full) - `dmesg` from a boot with `drm.debug=0xe log_buf_len=4M ignore_loglevel` (when requested) - `lspci -vvnn`, `dmidecode` system/BIOS - EDID (`edid-decode`) and `xrandr --verbose` - `i915_edp_psr_status`, `i915_dmc_info`, `i915_display_info` - `package_cstate_show`, `cpupower idle-info`, `/proc/cmdline`, `uname -a` - `smartctl -a /dev/nvme0` ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: m0k4s1n3s 4248 F.... wireplumber /dev/snd/controlC0: m0k4s1n3s 4248 F.... wireplumber /dev/snd/seq: m0k4s1n3s 4232 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 17:12:18 2026 InstallationDate: Installed on 2026-11-03 (8 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 1532:0233 Razer USA, Ltd Blade 15 (2018) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Razer Blade ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-42-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash i915.enable_psr=0 intel_idle.max_cstate=4 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux Title: Razer Blade 2019 (i7-8750H/UHD 630/144 Hz eDP): hard freeze with last frame retained; stable with i915.enable_psr=0 + intel_idle.max_cstate=4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Razer dmi.bios.version: 1.08 dmi.board.name: C1_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.08:bd05/21/2019:br1.8:efr1.3:svnRazer:pnBlade:pvr1.04:rvnRazer:rnC1_MB:rvr:cvnRazer:ct10:cvr:skuRZ09-02386G91:pfa1A582000RazerBlade: dmi.product.family: 1A582000 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02386G91 dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174549/+subscriptions

[Bug 2173618] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2173618/+attachment/6018185/+files/Lspci.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173618 Title: [Regression] No sound on various laptops with 7.0.0-43-generic: "CODEC DAI cs35l56-ot25 not registered" Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Confirmed Bug description: Summary ------- Since upgrading to kernel 7.0.0-43-generic, the internal audio on my Dell XPS 14 9440 no longer works. No sound card is registered and only "Dummy Output" is available. Internal speakers, headphone jack and internal microphone are all unavailable. Hardware -------- - Machine: Dell Inc. XPS 14 9440/0H14N3, BIOS 1.12.1 02/14/2025 - Audio controller: Intel Meteor Lake-P HD Audio Controller [0000:00:1f.3] (driver: sof-audio-pci-intel-mtl, SoundWire enabled) - Codecs on SoundWire: Cirrus Logic CS42L43 (headset/jack) + 4x Cirrus Logic CS35L56 Rev B0 OTP3 amplifiers (fw 3.4.4) Software -------- - Ubuntu [VERSION] - Kernel: 7.0.0-43-generic #43-Ubuntu (Ubuntu 7.0.0-43.43-generic 7.0.14) - SOF firmware: intel/sof-ipc4/mtl/sof-mtl.ri, booted version 2.14.1.1 What happens ------------ The SOF DSP firmware boots successfully, and the CS42L43 and all four CS35L56 amplifiers probe and report their device IDs. However, the sof_sdw machine driver never registers the card. The following message is repeated (deferred probe) throughout the session: sof_sdw sof_sdw: ASoC: CODEC DAI cs35l56-ot25 not registered (seen at 44.5 s, 46.4 s, 57.5 s, 57.7 s, 108.2 s, 108.4 s, 204.4 s, 204.6 s after boot) No topology is loaded, no "sof-soundwire" card appears, and `aplay -l` lists no sound card. It looks like the sof_sdw machine driver expects a CS35L56 DAI name ("cs35l56-ot25") that the cs35l56 codec driver does not register. Relevant dmesg excerpt ---------------------- sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 4 sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 0 sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.14.1.1 cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03 cs35l56 sdw:0:2:01fa:3556:01:3: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:1: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:2:01fa:3556:01:2: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:0: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) sof_sdw sof_sdw: ASoC: CODEC DAI cs35l56-ot25 not registered Regression ---------- Audio works with kernel 7.0.0-42-generic. Audio is broken with kernel 7.0.0-43-generic. Expected result --------------- The sof-soundwire card is registered and the internal speakers, headphone jack and microphone work, as with the previous kernel. Steps to reproduce ------------------ 1. Boot a Dell XPS 14 9440 with kernel 7.0.0-43-generic. 2. Open sound settings: only "Dummy Output" is available. 3. Run `sudo dmesg | grep sof_sdw`: the "CODEC DAI cs35l56-ot25 not registered" message is shown repeatedly. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: npiganeau 3493 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Nov 7 10:51:14 2026 InstallationDate: Installed on 2025-05-28 (528 days ago) InstallationMedia: Kubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: Dell Inc. XPS 14 9440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=ac0b393d-6815-45cc-8e3f-3deac7ae0f95 ro quiet splash kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-04 (34 days ago) dmi.bios.date: 02/14/2025 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0H14N3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd02/14/2025:br1.12:efr1.23:svnDellInc.:pnXPS149440:pvr:rvnDellInc.:rn0H14N3:rvrA00:cvnDellInc.:ct10:cvr:sku0C6B:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 14 9440 dmi.product.sku: 0C6B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173618/+subscriptions

[Bug 2173618] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2173618/+attachment/6018184/+files/CurrentDmesg.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173618 Title: [Regression] No sound on various laptops with 7.0.0-43-generic: "CODEC DAI cs35l56-ot25 not registered" Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Confirmed Bug description: Summary ------- Since upgrading to kernel 7.0.0-43-generic, the internal audio on my Dell XPS 14 9440 no longer works. No sound card is registered and only "Dummy Output" is available. Internal speakers, headphone jack and internal microphone are all unavailable. Hardware -------- - Machine: Dell Inc. XPS 14 9440/0H14N3, BIOS 1.12.1 02/14/2025 - Audio controller: Intel Meteor Lake-P HD Audio Controller [0000:00:1f.3] (driver: sof-audio-pci-intel-mtl, SoundWire enabled) - Codecs on SoundWire: Cirrus Logic CS42L43 (headset/jack) + 4x Cirrus Logic CS35L56 Rev B0 OTP3 amplifiers (fw 3.4.4) Software -------- - Ubuntu [VERSION] - Kernel: 7.0.0-43-generic #43-Ubuntu (Ubuntu 7.0.0-43.43-generic 7.0.14) - SOF firmware: intel/sof-ipc4/mtl/sof-mtl.ri, booted version 2.14.1.1 What happens ------------ The SOF DSP firmware boots successfully, and the CS42L43 and all four CS35L56 amplifiers probe and report their device IDs. However, the sof_sdw machine driver never registers the card. The following message is repeated (deferred probe) throughout the session: sof_sdw sof_sdw: ASoC: CODEC DAI cs35l56-ot25 not registered (seen at 44.5 s, 46.4 s, 57.5 s, 57.7 s, 108.2 s, 108.4 s, 204.4 s, 204.6 s after boot) No topology is loaded, no "sof-soundwire" card appears, and `aplay -l` lists no sound card. It looks like the sof_sdw machine driver expects a CS35L56 DAI name ("cs35l56-ot25") that the cs35l56 codec driver does not register. Relevant dmesg excerpt ---------------------- sof-audio-pci-intel-mtl 0000:00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 4 sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 0 sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.14.1.1 cs42l43 sdw:0:0:01fa:4243:01: devid: 0x042a43, rev: 0xa1, otp: 0x03 cs35l56 sdw:0:2:01fa:3556:01:3: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:1: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:2:01fa:3556:01:2: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) cs35l56 sdw:0:3:01fa:3556:01:0: Cirrus Logic CS35L56 Rev B0 OTP3 fw:3.4.4 (patched=0) sof_sdw sof_sdw: ASoC: CODEC DAI cs35l56-ot25 not registered Regression ---------- Audio works with kernel 7.0.0-42-generic. Audio is broken with kernel 7.0.0-43-generic. Expected result --------------- The sof-soundwire card is registered and the internal speakers, headphone jack and microphone work, as with the previous kernel. Steps to reproduce ------------------ 1. Boot a Dell XPS 14 9440 with kernel 7.0.0-43-generic. 2. Open sound settings: only "Dummy Output" is available. 3. Run `sudo dmesg | grep sof_sdw`: the "CODEC DAI cs35l56-ot25 not registered" message is shown repeatedly. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: npiganeau 3493 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Nov 7 10:51:14 2026 InstallationDate: Installed on 2025-05-28 (528 days ago) InstallationMedia: Kubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: Dell Inc. XPS 14 9440 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=ac0b393d-6815-45cc-8e3f-3deac7ae0f95 ro quiet splash kvm.enable_virt_at_load=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-04 (34 days ago) dmi.bios.date: 02/14/2025 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0H14N3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd02/14/2025:br1.12:efr1.23:svnDellInc.:pnXPS149440:pvr:rvnDellInc.:rn0H14N3:rvrA00:cvnDellInc.:ct10:cvr:sku0C6B:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 14 9440 dmi.product.sku: 0C6B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173618/+subscriptions

[Bug 2174473] Re: Btrfs zoned: ENOSPC/EAGAIN transaction abort and forced readonly on WD host-managed SMR (Ubuntu 26.04)

** 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/2174473 Title: Btrfs zoned: ENOSPC/EAGAIN transaction abort and forced readonly on WD host-managed SMR (Ubuntu 26.04) Status in linux package in Ubuntu: New Bug description: **Impact** Ubuntu Server 26.04 LTS experiences recurring Btrfs zoned filesystem failures on a 27 TB Western Digital host-managed SMR drive. Write operations fail despite substantial available space, and the filesystem can abort a transaction and switch to read-only. This prevents reliable use of the filesystem and presents a risk of incomplete writes or data loss. **Hardware and filesystem** - Drive: WDC WSH722870ALE604, 27 TB, host-managed SMR - Filesystem: Btrfs zoned, single-device - Zone size: 256 MiB - Filesystem UUID: 42bc4deb-1694-419f-96ea-1843a0a4f8d2 - Distribution: Ubuntu Server 26.04 LTS - Storage controller: Broadcom / LSI SAS9305-16i (SAS3224), using the mpt3sas kernel driver **Affected kernel versions** - 7.0.0-34-generic: transaction abort with EAGAIN (-11), followed by forced read-only - 7.0.0-42-generic: repeated ENOSPC (-28) errors during writes of large files, followed by filesystem failure - 7.0.0-43-generic: installed but not tested for this issue **Observed behavior** On November 7, 2026, kernel 7.0.0-34-generic reported: BTRFS error (device sdg): error while writing out transaction: -11 BTRFS warning (device sdg): Skipping commit of aborted transaction. BTRFS: Transaction aborted (error -11) BTRFS: error (device sdg state A) in cleanup_transaction:2060: errno=-11 unknown BTRFS info (device sdg state EA): forced readonly Previously, on kernel 7.0.0-42-generic, writing large media files repeatedly produced: BTRFS error (device sdg): cow_file_range failed ...: -28 BTRFS error (device sdg): failed to run delalloc range ...: -28 At the time of the November 7 failure, Btrfs reported: Device size: 24.56 TiB Device unallocated: 10.65 TiB Device zone unusable: 251.31 GiB Free (estimated): 10.86 TiB All Btrfs device error counters were zero, including read, write, flush, corruption and generation errors. Dynamic and periodic block-group reclaim were disabled. The corresponding reclaim counters were zero. **Expected behavior** Btrfs should successfully allocate space and complete transactions when sufficient usable space is available, without unexpectedly aborting transactions or forcing the filesystem into read-only mode. **Actual behavior** Write failures and transaction aborts occur intermittently during filesystem activity. The issue has been observed on multiple Ubuntu kernel versions. After the transaction abort, the filesystem becomes read-only and cannot accept further writes. **Related upstream development** I have reported the issue directly to the Linux Btrfs developers: https://lore-kernel.gnuweeb.org/linux- btrfs/e3261fe5-4b98-47e6-ae66-d4af05caa621@gmail.com/ Related Btrfs zoned patch discussion: https://lore-kernel.gnuweeb.org/linux- btrfs/20261110080932.1205332-1-johannes.thumshirn@wdc.com/ A broader Btrfs zoned fixes series by Dongjiang Zhu has also shown promising testing results on similar host-managed SMR hardware. The precise fix or combination of fixes required for this Ubuntu system has not yet been confirmed. **Request for Ubuntu Kernel Team** Please investigate this issue and evaluate backporting the relevant upstream Btrfs zoned fixes to the Ubuntu 26.04 LTS (Resolute) kernel through the Stable Release Update (SRU) process once the fixes have been accepted and validated upstream. I can provide complete kernel traces, filesystem usage statistics and additional read-only diagnostics. The affected filesystem contains important data without a complete backup, so testing experimental kernels or potentially destructive recovery procedures is not currently possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174473/+subscriptions

[Bug 2174479] Re: Title: HP Spectre x360 13-ac0XX: side volume buttons send no events in tablet mode; INT33D3 platform device has no driver bound

** 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/2174479 Title: Title: HP Spectre x360 13-ac0XX: side volume buttons send no events in tablet mode; INT33D3 platform device has no driver bound Status in linux package in Ubuntu: New Bug description: System: - HP Spectre x360 Convertible 13-ac0XX - BIOS F.33 (HP lists F.52 Rev.A, 2020, not installed) - Ubuntu 26.04.1 LTS, kernel 7.0.0-43-generic Problem: The physical volume button on the side of the laptop does nothing in tablet mode. The keyboard F-row volume keys work in laptop mode (KEY_VOLUMEUP/KEY_VOLUMEDOWN seen on event3 "AT Translated Set 2 keyboard"). Tablet mode itself is detected correctly (SW_TABLET_MODE toggles state 1/0 on "Intel Virtual Switches"). What I tested in tablet mode while pressing the side button: - sudo libinput debug-events --show-keycodes: no events - sudo evtest on "Intel Virtual Buttons" (event9): no events, although the device advertises KEY_VOLUMEUP, KEY_VOLUMEDOWN, KEY_POWER, KEY_LEFTMETA, KEY_ROTATE_LOCK_TOGGLE Drivers loaded (lsmod): hp_wmi, intel_vbtn, soc_button_array, sparse_keymap, wmi ACPI findings: - /sys/bus/acpi/devices contains INT33D0:00, INT33D3:00, INT33D6:00 - dmesg shows input devices created only for INT33D6:00 (Intel Virtual Buttons, Intel Virtual Switches) - INT33D3:00 (hid = INT33D3) has a platform device in /sys/bus/platform/devices/ but no driver is bound to it - /sys/bus/platform/drivers/soc_button_array/ lists no bound devices Other log lines (may be unrelated): - hp-wmi: Failed to apply initial fan settings: -22 - ACPI Error: Aborting method \_SB.WMID.WQBE (AE_AML_BUFFER_LIMIT) Expected: side volume button reports KEY_VOLUMEUP/KEY_VOLUMEDOWN in tablet mode. Question: should INT33D3 be handled by an existing driver on this model? ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: yonie 4020 F.... wireplumber /dev/snd/seq: yonie 4005 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 13:56:12 2026 InstallationDate: Installed on 2026-08-29 (77 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ac0XX 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-43-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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2017 dmi.bios.release: 15.33 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 94.60 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.33:bd06/20/2017:br15.33:efr94.60:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:sku1GN65EA#ABT:pfa103C_5335KVHPSpectre: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ac0XX dmi.product.sku: 1GN65EA#ABT dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174479/+subscriptions

[Bug 2174486] Re: realtek pci network card not working

** 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/2174486 Title: realtek pci network card not working Status in linux package in Ubuntu: New Bug description: after linux mint kernal update to 7.0.0-42 / 43, my realtek pci network card does not connect to the internet or to my local network anymore, but when i load kernal 7.0.0-38 it work perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174486/+subscriptions

[Bug 2174495] Re: iMac late 2015 (Cirrus Logic CS4208): internal speakers silent, no Speaker control

** 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/2174495 Title: iMac late 2015 (Cirrus Logic CS4208): internal speakers silent, no Speaker control Status in linux package in Ubuntu: New Bug description: Hardware: iMac late 2015 (MODEL) Codec: Cirrus Logic CS4208 (plus Intel Broadwell HDMI) Problem: Internal speakers produce no sound. The headphone socket works normally. This has been the case since installing Ubuntu (also on the live USB). Findings: - alsamixer on the PCH card shows Master, Headphone, PCM and mic controls, but no Speaker control. - The codec reports the internal speakers on digital pins: Node 0x1d [Pin Complex] 8-Channels Digital Pin Default 0x90100110: [Fixed] Speaker at Int Node 0x1e [Pin Complex] 8-Channels Digital Pin Default 0x90100112: [Fixed] Speaker at Int The headphone output is on analogue pin 0x10 (HP Out), which works. - Tried snd-hda-intel model=mbp11 and model=mba6 (confirmed applied via /sys/module/snd_hda_intel/parameters/model). Neither made any difference. It looks like the speakers are driven over the CS4208's digital output to an external amplifier, which Linux does not currently support. Happy to run tests or provide more output if useful. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jonwakeman 3025 F.... wireplumber /dev/snd/controlC0: jonwakeman 3025 F.... wireplumber /dev/snd/seq: jonwakeman 3019 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 22:00:49 2026 InstallationDate: Installed on 2026-11-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Apple Inc. iMac16,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=f98ae0b7-a557-41f2-86e1-92fe011a36ea ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 489.0.0.0.0 dmi.board.name: Mac-A369DDC4E67F1C45 dmi.board.vendor: Apple Inc. dmi.board.version: iMac16,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-A369DDC4E67F1C45 dmi.modalias: dmi:bvnAppleInc.:bvr489.0.0.0.0:bd10/07/2023:br0.1:svnAppleInc.:pniMac16,1:pvr1.0:rvnAppleInc.:rnMac-A369DDC4E67F1C45:rvriMac16,1:cvnAppleInc.:ct9:cvrMac-A369DDC4E67F1C45:sku:pfa: dmi.product.name: iMac16,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174495/+subscriptions

[Bug 2153096] Re: IPU6 webcam (OV2740) on X1 Nano fails on kernel 7.0.0-14/-15: int3472 cannot find GPIO chip INTC1096:00, VSC chain doesn't come up

Same model here (ThinkPad X1 Nano Gen 2, 21E80013US, BIOS N3IET54W 1.34, i7-1280P), Linux Mint 22.3 (noble base), tested with HWE 7.0.0-43 and 6.17.0-42. Same symptom: sensor and /dev/video* present, but no usable frames. Sharing my findings in case they help others and narrow the root cause. 1. The kernel capture path works. After letting libcamera configure the media graph once (cam -c1 -C2 -s role=raw), direct capture from the ISYS node with plain MMAP buffers is clean: v4l2-ctl -d /dev/video8 --stream-mmap=4 --stream-count=60 → BA10 1932x1092, consecutive sequence numbers, steady 30 fps, zero csi2-1 error messages, and the raw Bayer data contains a correct image. 2. Streaming through libcamera fails. Tested with libcamera 0.8.0 built from source, SoftISP in both CPU and GPU mode. Every libcamera session produces csi2-1 error messages (Transfer FIFO overflow, inter-frame packets discarded, CRC / packet header errors, and sometimes “stream stop time out”). Completed requests report bytesused: 0 and garbage sequence numbers and timestamps, so SoftISP outputs black frames. Even role=raw requests come back flagged this way. I suspect the buffer import path (libcamera uses DMABUF, while v4l2-ctl MMAP works), but I have not confirmed this. 3. Sensor control writes while streaming cause CSI-2 errors. In one test I changed each control during a clean v4l2-ctl stream: exposure: 0 errors analogue_gain: 7 errors digital_gain: 3 errors vertical_blanking: 4 errors Frames keep coming in plain V4L2. Gain changes from AGC therefore look harmful. 4. IVSC is a red herring on non-Computer-Vision SKUs. The DSDT puts SPFD (INTC1094) under \_SB.PC00.SPI1 unless CVFS == 2. On my unit the BIOS sets CVFS = 0 (CUPN = 8). When I forced CVFS = 2 with a small SSDT, spi- INTC1094:00 appeared on the LJCA SPI bus, but vsc-tp fails with -22 because the wakeupfw LJCA GPIO line (VGPO pin 1) is not valid (gpiochip_line_is_valid = 0). I believe this unit has no IVSC fitted: Computer Vision is optional on this model. Without IVSC the direct ov2740 → CSI2 graph is correct. Working workaround (no libcamera at runtime): Set fixed sensor controls before streaming (exposure=1102, analogue_gain=512). Stream with v4l2-ctl --stream-mmap ... --stream-to=-. Debayer with ffmpeg (-pixel_format bayer_grbg16le -video_size 1952x1092), subtract black level 64, scale 10→16-bit, apply per-channel gains. Output to v4l2loopback (exclusive_caps=1). For simple auto-exposure, adjust only the exposure control. This works in browsers and video-call apps at about 28-30 fps with Secure Boot enabled. I can share the script if useful. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153096 Title: IPU6 webcam (OV2740) on X1 Nano fails on kernel 7.0.0-14/-15: int3472 cannot find GPIO chip INTC1096:00, VSC chain doesn't come up Status in linux package in Ubuntu: New Bug description: Thanks in advance for taking a look. I've revised this description after some follow-up testing; I think my original framing pointed at the wrong thing. What I'm seeing: The webcam on my ThinkPad X1 Nano (Gen 2, OV2740 behind IPU6) currently does not produce frames on either 7.0.0-14 or 7.0.0-15. libcamera and pipewire both see an `ov2740` device, `/dev/video*` are populated, and the IPU6 driver seems happy: intel-ipu6 0000:00:05.0: Found supported sensor INT3474:01 intel-ipu6 0000:00:05.0: Connected 1 cameras But every app that opens the camera fails identically: spa.v4l2: /dev/video0: VIDIOC_S_PARM: Inappropriate ioctl for device spa.v4l2: '/dev/video0' VIDIOC_STREAMON: Link has been severed pw.node: (v4l2_input.pci-0000_00_05.0-110) suspended -> error (Start error: Link has been severed) Cheese, Snapshot, Firefox, Chromium and Zoom all behave the same way. BIOS privacy is ok and the physical toggle has been checked. The kernel-side warnings line up with what I'd expect if the VSC chain never comes up: int3472-discrete INT3472:05: cannot find GPIO chip INTC1096:00, deferring int3472-discrete INT3472:06: cannot find GPIO chip INTC1096:00, deferring ov2740 i2c-INT3474:01: supply AVDD not found, using dummy regulator ov2740 i2c-INT3474:01: supply DOVDD not found, using dummy regulator ov2740 i2c-INT3474:01: supply DVDD not found, using dummy regulator `mei_vsc_hw` is loaded but unbound. `mei_vsc`, `intel_vsc`, `ivsc_csi`, `ivsc_ace` aren't loaded at all. The `INT3472:05/06` deferrals are the chain that powers the OV2740 rails, which is presumably why ov2740 ends up on dummy regulators. What I now believe could be a more interesting (frustrating?) bug than a kernel-version regression: * The camera **was** working on my stock 26.04 install on 2026-04-23. * That install pulled in `linux-image-generic-hwe-26.04 → 7.0.0-14.14`. The same `.14` deb is still installed today. * `linux-firmware` is still at `20260319.git217ca6e4`, libcamera at 0.7.0-1, pipewire/wireplumber at 1.6.2-1 / 0.5.13-1 — none have been upgraded since install (per `/var/log/apt/history.log` and `/var/log/dpkg.log`). * BIOS is unchanged (N3IET53W 1.33, 2025-12-03), `fwupdmgr get-history` is empty, `/etc/modprobe.d/` has nothing camera-relevant, kernel cmdline is stock (`ro quiet splash crashkernel=…`). So as best I can tell, the same kernel/firmware/userspace binaries that worked on day one are now failing, without an apt-tracked change between those two states. The HWE bump from .14 to .15 in my original report was just the moment I noticed. My best guess (and I'd love to be told if it's silly) is that this is a non-deterministic probe ordering issue around the USB-LJCA bridge — the INTC1096 ACPI companion is present at `\_SB_.PC00.XHCI.RHUB.HS08.VGPO` but its GPIO chip never gets registered, so int3472 can't find it, so the rails never come up, so VSC never starts, so streamon severs the link. I don't knw why this would sometimes succeed and sometimes not on otherwise identical software. ACPI layout summary (full data in attached diagnostics): \_SB_.PC00.SPI1.SPFD HID INTC1094 (mei_vsc_hw match) \_SB_.PC00.SPI1.SPFD.CVFD HID INTC1095 \_SB_.PC00.XHCI.RHUB.HS08.VGPO HID INTC1096 (GPIO chip never registers) \_SB_.PC00.XHCI.RHUB.HS08.VIC0/1 HID INTC1097 \_SB_.PC00.XHCI.RHUB.HS08.VSPI HID INTC1098 Side notes in case relevant: * The PCH SPI controller (PCI 0000:00:1f.5, spi0) has one child for the BIOS flash; spi-nor fails JEDEC ID on it. I think this is unrelated. * The Intel USB-LJCA bridge (8086:0b63) at HS08 / INTC1098 brings up spi1 via `spi_ljca`; `spi1` has no children (`waiting_for_supplier=0`). * I have not tried a 6.x kernel and many other distros — my recollection is the camera also did not work on 6.x for me even with the Intel patches, so I don't think rolling back further is productive. Attached `diagnostics.txt` (filed initially against 7.0.0-15) and `diagnostics-7.0.0-14.txt` (captured today on 7.0.0-14) have DMI, package versions, lsmod, lspci/lsusb, the spi_master tree, the relevant ACPI nodes, and the IPU6/MEI/VSC/OV2740/LJCA kernel and libcamera/pipewire log lines. They're the same shape so they can be diffed directly. Happy to do whatever's useful: capture across cold-boot/warm-boot/suspend cycles, watch whether the INTC1096 GPIO chip ever registers across multiple boots, try unbinding/rebinding `usb_ljca`, or run with debug options on `int3472`/`mei_vsc`/`gpio_ljca`. --- ProblemType: Bug ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: atb 7927 F.... pipewire atb 7941 F.... wireplumber /dev/snd/seq: atb 7927 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-05-17 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21E8002YSG Package: linux-image-7.0.0-14-generic 7.0.0-14.14 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=61e8b5c4-2752-445a-93d2-a68c8bb7dd3c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Tags: resolute wayland-session Uname: Linux 7.0.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/03/2025 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: N3IET53W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 21E8002YSG dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.21 dmi.modalias: dmi:bvnLENOVO:bvrN3IET53W(1.33):bd12/03/2025:br1.33:efr1.21:svnLENOVO:pn21E8002YSG:pvrThinkPadX1NanoGen2:rvnLENOVO:rn21E8002YSG:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21E8_BU_Think_FM_ThinkPadX1NanoGen2:pfaThinkPadX1NanoGen2: dmi.product.family: ThinkPad X1 Nano Gen 2 dmi.product.name: 21E8002YSG dmi.product.sku: LENOVO_MT_21E8_BU_Think_FM_ThinkPad X1 Nano Gen 2 dmi.product.version: ThinkPad X1 Nano Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153096/+subscriptions

[Bug 2172131] Re: XPS 13 9345 (Snapdragon X Elite): fan state fixed at boot, never adjusts until power cycle

Confirming that the in-review dell-xps-ec v8 patch series (https://lore.kernel.org/r/20261026-dell- xps-9345-ec-v8-0-251c2cbfbc6c@vinarskis.com), applied together with Liviu Nicoara's thermal zones v2 patch, fixes the fan on my XPS 13 9345 (Snapdragon X Elite). I built it on top of Ubuntu-7.3.0-10.10 on Ubuntu 26.10 with CONFIG_EC_DELL_XPS=m and the updated device tree. After rebooting, dell_xps_ec binds at i2c 5-003b with no errors, the fan spins up under load and slows down as it cools, and CPU temperatures dropped from about 95°C to 75°C. Thanks to the patch authors. It would be great to see this picked up in an Ubuntu kernel. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172131 Title: XPS 13 9345 (Snapdragon X Elite): fan state fixed at boot, never adjusts until power cycle Status in linux package in Ubuntu: New Bug description: Hardware: Dell XPS 13 9345 (Snapdragon X Elite), Ubuntu on arm64, kernel 7.3.0-9-generic. Problem: The fan's state is set only at power-on and never changes afterward. If it boots with the fan off, it stays off while the laptop gets very hot. If it's on, it stays on. Only a full power cycle changes it. Details: - lm-sensors shows all the CPU/GPU/NSP thermal zones reading normally, but no fan device or fan control is exposed at all. - It looks like the embedded controller isn't getting thermal or system-state updates from the OS, so it never changes fan speed after boot. This doesn't happen on Windows. - Firmware is up to date per fwupd. Expected: Fan speed follows temperature, like it does on Windows. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic aarch64 ApportVersion: 2.36.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tyler-wilson 4070 F.... pipewire tyler-wilson 4309 F.... wireplumber /dev/snd/pcmC0D1p: tyler-wilson 4070 F...m pipewire /dev/snd/seq: tyler-wilson 4070 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 13:31:31 2026 InstallationDate: Installed on 2026-10-21 (4 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official arm64 (20261010) Lspci-vt: -[0004:00]---00.0-[01-ff]----00.0 Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] -[0006:00]---00.0-[01-ff]----00.0 Sandisk Corp PC SN740 NVMe SSD (DRAM-less) MachineType: Dell Inc. XPS 13 9345 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=e94cd5a5-df71-4514-937a-b32bdcfffc7b ro clk_ignore_unused pd_ignore_unused cma=128M efi=noruntime quiet splash console=tty0 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) acpidump: dmi.bios.date: 07/ 9/2026 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.0 dmi.board.name: 0KY77V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.0:bd07/9/2026:br2.14:svnDellInc.:pnXPS139345:pvr:rvnDellInc.:rn0KY77V:rvrA00:cvnDellInc.:ct10:cvr:sku0C69:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 13 9345 dmi.product.sku: 0C69 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172131/+subscriptions

[Bug 2174495] [NEW] iMac late 2015 (Cirrus Logic CS4208): internal speakers silent, no Speaker control

Public bug reported: Hardware: iMac late 2015 (MODEL) Codec: Cirrus Logic CS4208 (plus Intel Broadwell HDMI) Problem: Internal speakers produce no sound. The headphone socket works normally. This has been the case since installing Ubuntu (also on the live USB). Findings: - alsamixer on the PCH card shows Master, Headphone, PCM and mic controls, but no Speaker control. - The codec reports the internal speakers on digital pins: Node 0x1d [Pin Complex] 8-Channels Digital Pin Default 0x90100110: [Fixed] Speaker at Int Node 0x1e [Pin Complex] 8-Channels Digital Pin Default 0x90100112: [Fixed] Speaker at Int The headphone output is on analogue pin 0x10 (HP Out), which works. - Tried snd-hda-intel model=mbp11 and model=mba6 (confirmed applied via /sys/module/snd_hda_intel/parameters/model). Neither made any difference. It looks like the speakers are driven over the CS4208's digital output to an external amplifier, which Linux does not currently support. Happy to run tests or provide more output if useful. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jonwakeman 3025 F.... wireplumber /dev/snd/controlC0: jonwakeman 3025 F.... wireplumber /dev/snd/seq: jonwakeman 3019 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 22:00:49 2026 InstallationDate: Installed on 2026-11-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Apple Inc. iMac16,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=f98ae0b7-a557-41f2-86e1-92fe011a36ea ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 489.0.0.0.0 dmi.board.name: Mac-A369DDC4E67F1C45 dmi.board.vendor: Apple Inc. dmi.board.version: iMac16,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-A369DDC4E67F1C45 dmi.modalias: dmi:bvnAppleInc.:bvr489.0.0.0.0:bd10/07/2023:br0.1:svnAppleInc.:pniMac16,1:pvr1.0:rvnAppleInc.:rnMac-A369DDC4E67F1C45:rvriMac16,1:cvnAppleInc.:ct9:cvrMac-A369DDC4E67F1C45:sku:pfa: dmi.product.name: iMac16,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** 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/2174495 Title: iMac late 2015 (Cirrus Logic CS4208): internal speakers silent, no Speaker control Status in linux package in Ubuntu: New Bug description: Hardware: iMac late 2015 (MODEL) Codec: Cirrus Logic CS4208 (plus Intel Broadwell HDMI) Problem: Internal speakers produce no sound. The headphone socket works normally. This has been the case since installing Ubuntu (also on the live USB). Findings: - alsamixer on the PCH card shows Master, Headphone, PCM and mic controls, but no Speaker control. - The codec reports the internal speakers on digital pins: Node 0x1d [Pin Complex] 8-Channels Digital Pin Default 0x90100110: [Fixed] Speaker at Int Node 0x1e [Pin Complex] 8-Channels Digital Pin Default 0x90100112: [Fixed] Speaker at Int The headphone output is on analogue pin 0x10 (HP Out), which works. - Tried snd-hda-intel model=mbp11 and model=mba6 (confirmed applied via /sys/module/snd_hda_intel/parameters/model). Neither made any difference. It looks like the speakers are driven over the CS4208's digital output to an external amplifier, which Linux does not currently support. Happy to run tests or provide more output if useful. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jonwakeman 3025 F.... wireplumber /dev/snd/controlC0: jonwakeman 3025 F.... wireplumber /dev/snd/seq: jonwakeman 3019 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Nov 14 22:00:49 2026 InstallationDate: Installed on 2026-11-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Apple Inc. iMac16,1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=f98ae0b7-a557-41f2-86e1-92fe011a36ea ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 489.0.0.0.0 dmi.board.name: Mac-A369DDC4E67F1C45 dmi.board.vendor: Apple Inc. dmi.board.version: iMac16,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-A369DDC4E67F1C45 dmi.modalias: dmi:bvnAppleInc.:bvr489.0.0.0.0:bd10/07/2023:br0.1:svnAppleInc.:pniMac16,1:pvr1.0:rvnAppleInc.:rnMac-A369DDC4E67F1C45:rvriMac16,1:cvnAppleInc.:ct9:cvrMac-A369DDC4E67F1C45:sku:pfa: dmi.product.name: iMac16,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174495/+subscriptions

[Bug 2174473] [NEW] Btrfs zoned: ENOSPC/EAGAIN transaction abort and forced readonly on WD host-managed SMR (Ubuntu 26.04)

Public bug reported: **Impact** Ubuntu Server 26.04 LTS experiences recurring Btrfs zoned filesystem failures on a 27 TB Western Digital host-managed SMR drive. Write operations fail despite substantial available space, and the filesystem can abort a transaction and switch to read-only. This prevents reliable use of the filesystem and presents a risk of incomplete writes or data loss. **Hardware and filesystem** - Drive: WDC WSH722870ALE604, 27 TB, host-managed SMR - Filesystem: Btrfs zoned, single-device - Zone size: 256 MiB - Filesystem UUID: 42bc4deb-1694-419f-96ea-1843a0a4f8d2 - Distribution: Ubuntu Server 26.04 LTS - Storage controller: Broadcom / LSI SAS9305-16i (SAS3224), using the mpt3sas kernel driver **Affected kernel versions** - 7.0.0-34-generic: transaction abort with EAGAIN (-11), followed by forced read-only - 7.0.0-42-generic: repeated ENOSPC (-28) errors during writes of large files, followed by filesystem failure - 7.0.0-43-generic: installed but not tested for this issue **Observed behavior** On November 7, 2026, kernel 7.0.0-34-generic reported: BTRFS error (device sdg): error while writing out transaction: -11 BTRFS warning (device sdg): Skipping commit of aborted transaction. BTRFS: Transaction aborted (error -11) BTRFS: error (device sdg state A) in cleanup_transaction:2060: errno=-11 unknown BTRFS info (device sdg state EA): forced readonly Previously, on kernel 7.0.0-42-generic, writing large media files repeatedly produced: BTRFS error (device sdg): cow_file_range failed ...: -28 BTRFS error (device sdg): failed to run delalloc range ...: -28 At the time of the November 7 failure, Btrfs reported: Device size: 24.56 TiB Device unallocated: 10.65 TiB Device zone unusable: 251.31 GiB Free (estimated): 10.86 TiB All Btrfs device error counters were zero, including read, write, flush, corruption and generation errors. Dynamic and periodic block-group reclaim were disabled. The corresponding reclaim counters were zero. **Expected behavior** Btrfs should successfully allocate space and complete transactions when sufficient usable space is available, without unexpectedly aborting transactions or forcing the filesystem into read-only mode. **Actual behavior** Write failures and transaction aborts occur intermittently during filesystem activity. The issue has been observed on multiple Ubuntu kernel versions. After the transaction abort, the filesystem becomes read-only and cannot accept further writes. **Related upstream development** I have reported the issue directly to the Linux Btrfs developers: https://lore-kernel.gnuweeb.org/linux- btrfs/e3261fe5-4b98-47e6-ae66-d4af05caa621@gmail.com/ Related Btrfs zoned patch discussion: https://lore-kernel.gnuweeb.org/linux- btrfs/20261110080932.1205332-1-johannes.thumshirn@wdc.com/ A broader Btrfs zoned fixes series by Dongjiang Zhu has also shown promising testing results on similar host-managed SMR hardware. The precise fix or combination of fixes required for this Ubuntu system has not yet been confirmed. **Request for Ubuntu Kernel Team** Please investigate this issue and evaluate backporting the relevant upstream Btrfs zoned fixes to the Ubuntu 26.04 LTS (Resolute) kernel through the Stable Release Update (SRU) process once the fixes have been accepted and validated upstream. I can provide complete kernel traces, filesystem usage statistics and additional read-only diagnostics. The affected filesystem contains important data without a complete backup, so testing experimental kernels or potentially destructive recovery procedures is not currently possible. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs eagain enospc smr zoned ** Attachment added: "Full Btrfs kernel error log from November 7, 2026 (Ubuntu 7.0.0-34): EAGAIN (-11) transaction abort, stack trace and forced read-only." https://bugs.launchpad.net/bugs/2174473/+attachment/6018019/+files/btrfs-error.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2174473 Title: Btrfs zoned: ENOSPC/EAGAIN transaction abort and forced readonly on WD host-managed SMR (Ubuntu 26.04) Status in linux package in Ubuntu: New Bug description: **Impact** Ubuntu Server 26.04 LTS experiences recurring Btrfs zoned filesystem failures on a 27 TB Western Digital host-managed SMR drive. Write operations fail despite substantial available space, and the filesystem can abort a transaction and switch to read-only. This prevents reliable use of the filesystem and presents a risk of incomplete writes or data loss. **Hardware and filesystem** - Drive: WDC WSH722870ALE604, 27 TB, host-managed SMR - Filesystem: Btrfs zoned, single-device - Zone size: 256 MiB - Filesystem UUID: 42bc4deb-1694-419f-96ea-1843a0a4f8d2 - Distribution: Ubuntu Server 26.04 LTS - Storage controller: Broadcom / LSI SAS9305-16i (SAS3224), using the mpt3sas kernel driver **Affected kernel versions** - 7.0.0-34-generic: transaction abort with EAGAIN (-11), followed by forced read-only - 7.0.0-42-generic: repeated ENOSPC (-28) errors during writes of large files, followed by filesystem failure - 7.0.0-43-generic: installed but not tested for this issue **Observed behavior** On November 7, 2026, kernel 7.0.0-34-generic reported: BTRFS error (device sdg): error while writing out transaction: -11 BTRFS warning (device sdg): Skipping commit of aborted transaction. BTRFS: Transaction aborted (error -11) BTRFS: error (device sdg state A) in cleanup_transaction:2060: errno=-11 unknown BTRFS info (device sdg state EA): forced readonly Previously, on kernel 7.0.0-42-generic, writing large media files repeatedly produced: BTRFS error (device sdg): cow_file_range failed ...: -28 BTRFS error (device sdg): failed to run delalloc range ...: -28 At the time of the November 7 failure, Btrfs reported: Device size: 24.56 TiB Device unallocated: 10.65 TiB Device zone unusable: 251.31 GiB Free (estimated): 10.86 TiB All Btrfs device error counters were zero, including read, write, flush, corruption and generation errors. Dynamic and periodic block-group reclaim were disabled. The corresponding reclaim counters were zero. **Expected behavior** Btrfs should successfully allocate space and complete transactions when sufficient usable space is available, without unexpectedly aborting transactions or forcing the filesystem into read-only mode. **Actual behavior** Write failures and transaction aborts occur intermittently during filesystem activity. The issue has been observed on multiple Ubuntu kernel versions. After the transaction abort, the filesystem becomes read-only and cannot accept further writes. **Related upstream development** I have reported the issue directly to the Linux Btrfs developers: https://lore-kernel.gnuweeb.org/linux- btrfs/e3261fe5-4b98-47e6-ae66-d4af05caa621@gmail.com/ Related Btrfs zoned patch discussion: https://lore-kernel.gnuweeb.org/linux- btrfs/20261110080932.1205332-1-johannes.thumshirn@wdc.com/ A broader Btrfs zoned fixes series by Dongjiang Zhu has also shown promising testing results on similar host-managed SMR hardware. The precise fix or combination of fixes required for this Ubuntu system has not yet been confirmed. **Request for Ubuntu Kernel Team** Please investigate this issue and evaluate backporting the relevant upstream Btrfs zoned fixes to the Ubuntu 26.04 LTS (Resolute) kernel through the Stable Release Update (SRU) process once the fixes have been accepted and validated upstream. I can provide complete kernel traces, filesystem usage statistics and additional read-only diagnostics. The affected filesystem contains important data without a complete backup, so testing experimental kernels or potentially destructive recovery procedures is not currently possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174473/+subscriptions