[Bug 2169427] Re: Regression: 7.0.0-38-generic hangs during boot when NVIDIA driver loads; boots successfully with NVIDIA modules blacklisted; 7.0.0-34 works

** 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/2169427 Title: Regression: 7.0.0-38-generic hangs during boot when NVIDIA driver loads; boots successfully with NVIDIA modules blacklisted; 7.0.0-34 works Status in linux package in Ubuntu: New Bug description: I am running Kubuntu 24.04.5 amd64 with the HWE kernel stack. This is a regression between Ubuntu HWE kernels 7.0.0-34-generic and 7.0.0-38-generic. Working kernel 7.0.0-34-generic boots and operates normally on this system. Failing kernel 7.0.0-38-generic consistently hangs during early boot. With the normal quiet splash parameters, the last visible GRUB message is: Loading initial ramdisk ... Removing quiet splash and adding: loglevel=7 ignore_loglevel shows that the kernel actually progresses into hardware initialization before hanging. Near the end of the visible output are repeated ACPI errors involving: \_SB.PC00.RP01.PXSX._DSM.USRG AE_ALREADY_EXISTS CreateBufferField failure \_SB.PC00.RP01.PXSX._DSM PCI device 0000:02:00.0, corresponding to that ACPI path, is: NVIDIA Corporation AD103 [GeForce RTX 4070 Ti SUPER] [10de:2705] However, these same ACPI _DSM / AE_ALREADY_EXISTS errors also occur when booting the working 7.0.0-34-generic kernel. Under 7.0.0-34, boot continues after them and the NVIDIA DRM driver initializes normally. Therefore I do not believe the ACPI errors themselves are the regression. Important diagnostic result I edited the GRUB entry for 7.0.0-38-generic and added: module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm,nouveau systemd.unit=multi-user.target With the NVIDIA-related kernel modules blacklisted, 7.0.0-38 boots successfully. I can enter the LUKS disk-decryption password and the system reaches a text-mode TTY. There is no graphical desktop, as expected because the NVIDIA modules are blacklisted. Therefore the 7.0.0-38 boot failure appears to be associated with loading/initializing the NVIDIA driver rather than with the initramfs itself. Repair attempts already performed While booted into the working 7.0.0-34-generic kernel, I ran: sudo dpkg --configure -a sudo apt -f install sudo update-initramfs -u -k 7.0.0-38-generic sudo update-grub This did not change the behavior. 7.0.0-38 still hangs when NVIDIA is allowed to load. Reproducibility 1. Boot 7.0.0-38-generic normally. 2. System hangs during early kernel boot. 3. Reboot and select 7.0.0-34-generic: system boots normally. 4. Boot 7.0.0-38-generic with NVIDIA-related modules blacklisted: system boots successfully to a TTY. The failure has been reproduced multiple times. I am submitting this report while running another working kernel because 7.0.0-38-generic cannot boot normally far enough for me to run apport under that kernel. I have a photograph of the final console output from a failed 7.0.0-38 boot and will attach it to this report. In a sense, this is a security bug because I am forced to fall back to 7.0.0-34, which does not have all the security patches of -38. I'll also note that -38 failing to boot does not make the option of switching to 26.04 attractive. My understanding is that the 26.04 upgrade would install -38, possibly without a fallback. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-146-generic 6.8.0-146.146 ProcVersionSignature: Ubuntu 6.8.0-146.146-generic 6.8.12 Uname: Linux 6.8.0-146-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pm 3474 F.... wireplumber /dev/snd/controlC1: pm 3474 F.... wireplumber /dev/snd/controlC0: pm 3474 F.... wireplumber /dev/snd/seq: pm 3472 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Oct 3 13:02:30 2026 HibernationDevice: RESUME=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 InstallationDate: Installed on 2024-12-22 (651 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: CyberPowerPC GamingPC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-146-generic root=UUID=d7e17bac-b56c-4498-b5e0-e249bd682b7d ro quiet cryptdevice=UUID=c8b193ba-0124-495f-a549-091eb877b76a:cryptroot root=/dev/mapper/cryptroot splash resume=UUID=f2799cf1-38b5-43b9-80b1-9f330e95c354 "acpi_osi=Windows 2022" acpi_mask_gpe=0x6E vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-146-generic N/A linux-backports-modules-6.8.0-146-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2026 dmi.bios.release: 32.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3212 dmi.board.asset.tag: Default string dmi.board.name: Z890 MAX GAMING WIFI7 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3212:bd07/29/2026:br32.12:svnCyberPowerPC:pnGamingPC:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ890MAXGAMINGWIFI7:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuCPPC-SYSTEM-US: dmi.product.family: C Series dmi.product.name: GamingPC dmi.product.sku: CPPC-SYSTEM-US dmi.product.version: System Version dmi.sys.vendor: CyberPowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169427/+subscriptions

[Bug 2169378] [NEW] Add Realtek RT721_U and RT718 SoundWire audio support

Public bug reported: [Impact] Audio on new Dell Pro 5 All-in-One platforms is not fully supported on systems with the newer Realtek SoundWire codec variants. The driver lacks device matching and the variant-specific settings needed for playback, microphone capture, and headset setup. [Fix] Extend the existing codec driver to match the new variants and apply their register settings, headset calibration, and playback volume ranges. Add the new device to the shared SoundWire codec information table. ASoC: rt721: Add support for the RT721_U and RT718 codec variants https://patch.msgid.link/20260917104244.2512641-1-oder_chiou@realtek.com [Test Plan] Use systems with each newly supported codec variant. Boot the unpatched kernel and then the patched kernel with the same audio userspace. List the playback and capture devices: aplay -l arecord -l Select the speaker output and set a safe audible volume. Use the matching ALSA card and device numbers to test stereo playback: speaker-test -D plughw:CARD,DEVICE -c 2 -t wav -l 1 Plug in a headset, select its output, and repeat with its playback device. Select the headset microphone and record while speaking: arecord -D plughw:CARD,DEVICE -f S16_LE -r 48000 -c 1 -d 5 /tmp/realtek-mic.wav aplay /tmp/realtek-mic.wav Repeat the recording with the built-in microphone selected. Replace CARD and DEVICE with the numbers for each path. Without the support patch, the new device may not bind to the driver, or audio paths may fail because they use settings for the original variant. With the patch, the device binds and playback and capture work on each path. For the reset dependency, warm-reboot an affected system from Windows into Ubuntu and run the playback test. Without the reset fix, output can sound abnormal. With the fix, output sounds normal. [Where problems could occur] The changes affect the Realtek SoundWire codec driver and the shared SoundWire codec table. Wrong variant detection or volume ranges could cause silent, distorted, or unexpectedly loud playback. Wrong pin or calibration settings could break headset detection or microphone capture. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Tags: jira-somerville-4796 oem-priority somerville ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Tags added: jira-somerville-4796 oem-priority somerville -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169378 Title: Add Realtek RT721_U and RT718 SoundWire audio support Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Status in linux source package in Stonking: New Bug description: [Impact] Audio on new Dell Pro 5 All-in-One platforms is not fully supported on systems with the newer Realtek SoundWire codec variants. The driver lacks device matching and the variant-specific settings needed for playback, microphone capture, and headset setup. [Fix] Extend the existing codec driver to match the new variants and apply their register settings, headset calibration, and playback volume ranges. Add the new device to the shared SoundWire codec information table. ASoC: rt721: Add support for the RT721_U and RT718 codec variants https://patch.msgid.link/20260917104244.2512641-1-oder_chiou@realtek.com [Test Plan] Use systems with each newly supported codec variant. Boot the unpatched kernel and then the patched kernel with the same audio userspace. List the playback and capture devices: aplay -l arecord -l Select the speaker output and set a safe audible volume. Use the matching ALSA card and device numbers to test stereo playback: speaker-test -D plughw:CARD,DEVICE -c 2 -t wav -l 1 Plug in a headset, select its output, and repeat with its playback device. Select the headset microphone and record while speaking: arecord -D plughw:CARD,DEVICE -f S16_LE -r 48000 -c 1 -d 5 /tmp/realtek-mic.wav aplay /tmp/realtek-mic.wav Repeat the recording with the built-in microphone selected. Replace CARD and DEVICE with the numbers for each path. Without the support patch, the new device may not bind to the driver, or audio paths may fail because they use settings for the original variant. With the patch, the device binds and playback and capture work on each path. For the reset dependency, warm-reboot an affected system from Windows into Ubuntu and run the playback test. Without the reset fix, output can sound abnormal. With the fix, output sounds normal. [Where problems could occur] The changes affect the Realtek SoundWire codec driver and the shared SoundWire codec table. Wrong variant detection or volume ranges could cause silent, distorted, or unexpectedly loud playback. Wrong pin or calibration settings could break headset detection or microphone capture. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2169378/+subscriptions

[Bug 2167915] Re: Support Cirrus Logic CS42L45+CS35L63 on new Dell Slate NVL

** Description changed: [Impact] Dell Slate-2 Systems using Cirrus CS42L45 codec + CS35L63 amp need new SDCA feature support and the corresponding linux-firmware to have all audio function work + [Fix] ======= linux kernel ====== - [Fix] Need the following patches on 7.3 (which are already in Stonking) ee1811eacdbb soundwire: bus_type: Create IRQ mapping before calling driver probe() df036250d7d5 ASoC: SDCA: Remove sdca_function_data duplication 9557ec3f9c9f ASoC: SDCA: Add RJ support to class driver a158fe7b0c81 ASoC: SOF: Intel: NVL-S: add platform name ab463b465585 ASoC: SOF: Intel: NVL: add platform name - ====== linux-firmware ====== AMP FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2ded07e3da99f522881039f13595f34d54acdc74 [git.kernel.org] Codec FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=10f09227a370e02de71b584024c20dc8d3a02103 [git.kernel.org] - ====== firmware-sof ====== https://github.com/thesofproject/sof-bin/releases/tag/v2026.09 - [Test Plan] 1. Boot up The Dell Slate-2 NVL system with CS42L45+CS35L63 audio solution 2. Go to g-s-d for sound settings for audio intput/output device check 3. Make sure they're not Dummy for audio input/output 4. `aplay` to verify audio output function and `arecord` to verify audio input [Where problems could occur] It's new Dell system with Intel NVL, need firmware-sof + kernel SDCA for Intel NVL + linux-firmware to work. Need to make sure no regression on older platforms. Ex. Intel WCL, PTL...etc -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167915 Title: Support Cirrus Logic CS42L45+CS35L63 on new Dell Slate NVL Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in firmware-sof source package in Resolute: New Status in linux source package in Resolute: Invalid Status in linux-firmware source package in Resolute: New Status in firmware-sof source package in Stonking: New Status in linux source package in Stonking: Fix Released Status in linux-firmware source package in Stonking: New Bug description: [Impact] Dell Slate-2 Systems using Cirrus CS42L45 codec + CS35L63 amp need new SDCA feature support and the corresponding linux-firmware to have all audio function work [Fix] ======= linux kernel ====== Need the following patches on 7.3 (which are already in Stonking) ee1811eacdbb soundwire: bus_type: Create IRQ mapping before calling driver probe() df036250d7d5 ASoC: SDCA: Remove sdca_function_data duplication 9557ec3f9c9f ASoC: SDCA: Add RJ support to class driver a158fe7b0c81 ASoC: SOF: Intel: NVL-S: add platform name ab463b465585 ASoC: SOF: Intel: NVL: add platform name ====== linux-firmware ====== AMP FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2ded07e3da99f522881039f13595f34d54acdc74 [git.kernel.org] Codec FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=10f09227a370e02de71b584024c20dc8d3a02103 [git.kernel.org] ====== firmware-sof ====== https://github.com/thesofproject/sof-bin/releases/tag/v2026.09 [Test Plan] 1. Boot up The Dell Slate-2 NVL system with CS42L45+CS35L63 audio solution 2. Go to g-s-d for sound settings for audio intput/output device check 3. Make sure they're not Dummy for audio input/output 4. `aplay` to verify audio output function and `arecord` to verify audio input [Where problems could occur] It's new Dell system with Intel NVL, need firmware-sof + kernel SDCA for Intel NVL + linux-firmware to work. Need to make sure no regression on older platforms. Ex. Intel WCL, PTL...etc To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2167915/+subscriptions

[Bug 2169175] Re: Fix missing headset on Dell QCx1255 models

** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169175 Title: Fix missing headset on Dell QCx1255 models Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Bug description: [Impact] The headset microphone does not work on Dell QC1255 models. The earlier headphone pop-noise fix leaves out the headset-mode setup. [Fix] Chain the headset-microphone and headset-mode fixup after the headphone pop-noise fixup in the Realtek HDA codec driver. Upstream commit 608c0c8947f03069b651ace54538a115f5b23123 is in the sound tree and linux-next, It fixes the regression introduced by headphone pop-noise fix 97272a5704bf, which is in v7.2. [Test Plan] On an affected Dell QCx1255 models, plug in a headset with a microphone and select the headset microphone as the recording input. List the ALSA capture devices: arecord -l Record five seconds while speaking, using the card and device numbers shown above for the Realtek codec: arecord -D plughw:CARD,DEVICE -f S16_LE -r 48000 -c 1 -d 5 /tmp/headset-mic.wav aplay /tmp/headset-mic.wav Replace CARD and DEVICE with those numbers. Without the patch, the headset microphone does not record speech. With the patch, the recording contains speech from the headset microphone. [Where problems could occur] The change affects headset pin setup on Dell systems using this Realtek HDA fixup. If the chained fixup selects the wrong input pins, the headset microphone may still be silent or the built-in microphone may stop working. If the fixup changes headphone routing, headphone pop noise could return. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2169175/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-fde/5.15.0-1123.132)

All autopkgtests for the newly accepted linux-restricted-modules-azure-fde (5.15.0-1123.132) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, armhf, i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-fde [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 2169339] Re: [iMac18,2] BCM43602 Wi-Fi (brcmfmac) cannot associate on 7.3 kernels: DMAR DMA Read faults, firmware hangs; works with intel_iommu=off

** 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/2169339 Title: [iMac18,2] BCM43602 Wi-Fi (brcmfmac) cannot associate on 7.3 kernels: DMAR DMA Read faults, firmware hangs; works with intel_iommu=off Status in linux package in Ubuntu: New Bug description: On an iMac18,2 (2017) with a Broadcom BCM43602 [14e4:43ba] (subsystem Apple [106b:016e]), Wi-Fi no longer connects since the installed system moved to the 7.3 kernel. Booting with intel_iommu=off makes it work again. Wi-Fi worked in the Ubuntu 26.10 live session used to install the machine (kernel 7.2.0-5, image of 2026-09-15). The installer then upgraded to linux 7.3.0-5 and removed 7.2.0-5, and Wi-Fi has failed on every boot since (7.3.0-5, 7.3.0-6 and 7.3.0-8, 13 boots in total). I have no logs from the 7.2 live session, so I cannot tell whether the IOMMU was enabled there. What happens on a default boot: 1. brcmfmac loads, firmware starts, wlp3s0 appears, the initial scan works (the access point is listed with a strong signal). 2. As soon as association starts, the IOMMU reports two faults for the Wi-Fi device: DMAR: DRHD: handling fault status reg 2 DMAR: [DMA Read NO_PASID] Request device [0000:03:00.0] fault addr 0xfffa3000 [fault reason 0x06] PTE Read access is not set DMAR: [DMA Read NO_PASID] Request device [0000:03:00.0] fault addr 0xfffa5000 [fault reason 0x06] PTE Read access is not set (the addresses vary between boots, e.g. 0xfff64000 / 0xfff65000) 3. The firmware stops answering: ieee80211 phy0: brcmf_msgbuf_query_dcmd: Timeout on response for query command ieee80211 phy0: brcmf_get_assoc_ies: could not get assoc info (-5) 4. After a few minutes the control ring fills up: ieee80211 phy0: brcmf_msgbuf_tx_ioctl: Failed to reserve space in commonring ieee80211 phy0: brcmf_run_escan: error (-12) 5. NetworkManager: "association took too long, failing activation", reason 'ssid-not-found', retried forever. WORKAROUND Adding intel_iommu=off to the kernel command line. With it, on the same kernel (7.3.0-8-generic): no DMAR fault, no firmware timeout, association succeeds within seconds and traffic flows (IPv4 and IPv6). The usual BCM43602 workarounds were already in place and did not help: options brcmfmac feature_disable=0x82000 roamoff=1 options cfg80211 ieee80211_regdom=FR SYSTEM Release: Ubuntu 26.10 "Stonking Stingray" (development branch) Kernel: 7.3.0-8-generic (7.3.0-8.8, based on 7.3.0-rc5); also 7.3.0-5.5 and 7.3.0-6.6 Machine: Apple iMac18,2 Wi-Fi: Broadcom BCM43602 802.11ac [14e4:43ba] rev 01, subsystem Apple [106b:016e] Driver: brcmfmac (in-tree), firmware brcm/brcmfmac43602-pcie Firmware: BCM43602/1 wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c linux-firmware: 20260915.git1522c78a wpasupplicant: 2:2.11-2ubuntu2 Kernel config: CONFIG_INTEL_IOMMU_DEFAULT_ON=y, CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y, IOMMU default domain type "Translated", lazy TLB invalidation Secure Boot: not supported on this machine Note: a custom NVRAM file /lib/firmware/brcm/brcmfmac43602-pcie.txt was added on 2026-09-20 while trying to fix this. The failure already occurred on the boots before that file existed. Note: the logs attached automatically by apport come from a boot with intel_iommu=off (working). Kernel log excerpts from a failing boot (default command line) are attached separately as dmesg-failing- boot.txt. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-8-generic 7.3.0-8.8 ProcVersionSignature: Ubuntu 7.3.0-8.8-generic 7.3.0-rc5 Uname: Linux 7.3.0-8-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: parents 18057 F.... wireplumber /dev/snd/controlC1: parents 18057 F.... wireplumber /dev/snd/seq: parents 18053 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 22:10:14 2026 InstallationDate: Installed on 2026-09-19 (13 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Daily amd64 (20260915) MachineType: Apple Inc. iMac18,2 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-8-generic root=UUID=449c41b8-da4d-4c34-ad74-1f7a5e150bb0 ro quiet splash intel_iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 451.140.1.0.0 dmi.board.name: Mac-77F17D7DA9285301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac18,2 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77F17D7DA9285301 dmi.modalias: dmi:bvnAppleInc.:bvr451.140.1.0.0:bd04/11/2022:br0.1:svnAppleInc.:pniMac18,2:pvr1.0:rvnAppleInc.:rnMac-77F17D7DA9285301:rvriMac18,2:cvnAppleInc.:ct9:cvrMac-77F17D7DA9285301:sku:pfaiMac: dmi.product.family: iMac dmi.product.name: iMac18,2 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/2169339/+subscriptions

[Bug 2131077] Re: Add intel-speed-select to linux-tools-$(uname -r)

** Also affects: linux-vmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-lowlatency-hwe-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-vmware (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-vmware (Ubuntu Noble) Assignee: (unassigned) => Manuel Diewald (diewald) ** Changed in: linux-vmware (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux-vmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2131077 Title: Add intel-speed-select to linux-tools-$(uname -r) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-6.17 package in Ubuntu: Fix Committed Status in linux-hwe-6.8 package in Ubuntu: Fix Committed Status in linux-lowlatency package in Ubuntu: Fix Committed Status in linux-lowlatency-hwe-6.8 package in Ubuntu: Fix Released Status in linux-vmware package in Ubuntu: Invalid Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.17 source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: New Status in linux-lowlatency source package in Noble: Fix Released Status in linux-lowlatency-hwe-6.8 source package in Noble: New Status in linux-vmware source package in Noble: Fix Committed Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: SRU Justification: [Impact] The intel-speed-select utility provides more granular control and inspection capabilities for Intel CPUs with Intel Speed Select Technology (SST) support. This utility is built from Linux kernel sources. [Fix] Apply the patch "UBUNTU: [Packaging] Add intel-speed-select to linux-tools" from Resolute that builds and packages the intel-speed-select binary in a binary packaged named $(SRCPKG)-tools-$(ABIVER) under /usr/lib/$(SRCPKG)-tools-$(ABIVER). This applies only to Ubuntu kernel builds where do_tools_x86 is true. This patch is to be applied to Questing and Noble. It is a clean cherry pick to Questing, and a backport to Noble. It is already present in Resolute and newer. [Test Plan] 1. Build the generic kernel with this patch applied. 2. Verify the only additional file is the intel-speed-select utility: $ debdiff linux-tools-6.17.0-29.29_6.17.0-29.29_amd64.deb linux- tools-6.17.0-1029.29_6.17.0-1029.29_amd64.deb 3. Run intel-speed-select, verify the output is as expected. $ sudo /usr/lib/linux-tools-6.17.0-1030/intel-speed-select turbo-freq info -l 0 Intel(R) Speed Select Technology Executing on CPU model:173[0xad] Caching topology information package-0 die-0 powerdomain-0 cpu-0 speed-select-turbo-freq-properties bucket-0 high-priority-cores-count:24 high-priority-max-level-0-frequency(MHz):3900 high-priority-max-level-1-frequency(MHz):3900 ... [Where problems could occur] Any possible issues would likely affect the kernel tools packaging. The risk of regression is low, as this patch only adds a single binary to the $(SRCPKG)-tools-$(ABIVER) binary package. No wrapper scripts are added or modified. intel-speed-select can hep sysadmin on various cpu perf/freq related decission. Adding this to linux-tool would be very useful. https://docs.kernel.org/admin-guide/pm/intel-speed-select.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131077/+subscriptions

[Bug 2168310] Re: Kernel panic in __run_timers / __queue_work on HP Pavilion 15-cs3xxx, kernels 7.0.0-30 and 7.0.0-31

Hi, Thanks for submitting a bug report. When did you first notice this issue? Have you tried any earlier versions of the 7.0.0 kernel? It would really help to narrow down when this bug was introduced. If it is caused by the kernel ideally we would find the exact release that introduced it (e.g. -25 works but -26 doesn't). -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168310 Title: Kernel panic in __run_timers / __queue_work on HP Pavilion 15-cs3xxx, kernels 7.0.0-30 and 7.0.0-31 Status in linux package in Ubuntu: New Bug description: System repeatedly hangs or fully panics on Ubuntu 26.04, HP Pavilion Laptop 15-cs3xxx (BIOS F.21). Reproduced on both linux-image-7.0.0-30-generic and linux-image-7.0.0-31-generic, so it is not specific to one kernel build. Symptom: - Most occurrences: system freezes completely and must be hard-rebooted. - One occurrence produced a full kernel panic instead of a silent hang: "Kernel panic - not syncing: Fatal exception in interrupt", 67 seconds after boot, i.e. during early session/network startup rather than after prolonged use. Crash signature (consistent across all occurrences, captured via pstore): - RIP: __run_timers+0x1d8-0x1e0 or __queue_work.part.0+0x190/0x390 (kernel/workqueue.c:2351) - RAX/R12 = dead000000000122 — indicates a timer/work item's memory was already freed (poisoned list pointer) while still queued, i.e. a use-after-free in some driver's delayed_work/timer teardown. - Observed with the process context being, on different occasions: swapper/0 (idle), gnome-shell, and thunderbird-bin — so it is not tied to one specific userspace application; it appears to be triggered by network/Bluetooth related driver activity (iwlwifi, mac80211, bluetooth, btusb, btintel, btrtl, btmtk are loaded in every crash). Disabling network before opening Thunderbird reliably avoided the crash in my testing; enabling networking reliably reproduced it within seconds to a couple of minutes. Steps that reliably reproduce it: 1. Boot normally with Wi-Fi/Bluetooth enabled. 2. Open Thunderbird (snap or otherwise) and let mail sync over the network, OR simply use the desktop normally with networking active. 3. Within roughly 10 seconds to a few minutes, the workqueue WARNING/BUG fires and the system hangs or panics. Ruled out during troubleshooting: - Not specific to Thunderbird: also captured with gnome-shell and swapper/0 as the offending context. - Not caused by the NVIDIA driver: reproduced with the nvidia module fully unloaded/removed (dkms package removed) and prime-select set to intel-only. - Not a Secure Boot signing issue (unrelated "Key was rejected" errors were resolved separately and are not connected to this crash). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: javier2 2260 F.... wireplumber /dev/snd/seq: javier2 2228 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 22:27:46 2026 InstallationDate: Installed on 2025-11-02 (325 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANG=es_ES.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-31-generic root=UUID=0b5509e7-7678-4c83-922c-29cff4bee36e ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-13 (102 days ago) dmi.bios.date: 12/08/2023 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.36 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.36 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd12/08/2023:br15.21:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:sku7VM48EA#ABE:pfa103C_5335KVHPPavilion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 7VM48EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168310/+subscriptions

[Bug 2168012] Re: Include v4l2loopback in default modules set for 26.04

This bug is awaiting verification that the linux/7.0.0-39.39 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168012 Title: Include v4l2loopback in default modules set for 26.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Resolute: Fix Committed Bug description: == SRU Justification == -- Impact -- Before 26.04/Resolute the v4l2loopback module was build from DKMS and included in linux-modules. When switching to linux-main-modules (LMM) it was omitted from the additional dependencies for linux-modules and for that reason is no longer part of the default kernel installation (-generic). -- Fix -- Add packaging changes to depend on linux-main-modules-v4l2loopback-* from linux-modules. -- Testcase -- Before: installing linux-generic would not install the module After: installing linux-generic should have it -- Regression Potential -- Since there is no code change things to go wrong are packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168012/+subscriptions

[Bug 2169184] Re: thunderbird crashes whole system

Hi, Thanks for opening a bug report. This seems similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169091, can you please let me know if it matches your issue? If so we can mark this report as a duplicate. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169184 Title: thunderbird crashes whole system Status in linux package in Ubuntu: New Bug description: when i open thunderbird, after a few clicks system crashes with "kernel in panic reboot your system" removed thunderbird and installed it new, but same problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169184/+subscriptions

[Bug 2169185] Re: Dell XPS 13 9340: OV02C10 front camera image upside down (missing ipu-bridge DMI quirk)

** 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/2169185 Title: Dell XPS 13 9340: OV02C10 front camera image upside down (missing ipu- bridge DMI quirk) Status in linux package in Ubuntu: New Bug description: On a Dell XPS 13 9340 with Ubuntu 26.04.1 (kernel 7.0.0-38-generic, libcamera 0.7.0), the built-in OV02C10 camera works via libcamera/PipeWire, but the image is rotated by 180°. cam -p reports Rotation = 0. The sensor is mounted upside down and the firmware does not report the rotation. Upstream fixed this with the patch "media: ipu-bridge: Add upside-down sensor DMI quirk for Dell XPS 13 9340 and XPS 14 9440" by Hans de Goede (posted 2026-02-25, Cc: stable, Fixes: d5ebe3f7d13d, Red Hat bug 2440581). Please backport this quirk to the Ubuntu 26.04 kernel. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: user 26578 F.... pipewire user 26579 F.... wireplumber /dev/snd/seq: user 26578 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 1 18:51:50 2026 InstallationDate: Installed on 2024-08-09 (784 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. XPS 13 9340 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no username) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-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: Upgraded to resolute on 2026-10-01 (0 days ago) dmi.bios.date: 07/23/2026 dmi.bios.release: 1.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.29.0 dmi.board.name: 08214J 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.29.0:bd07/23/2026:br1.29:efr1.23:svnDellInc.:pnXPS139340:pvr:rvnDellInc.:rn08214J:rvrA00:cvnDellInc.:ct10:cvr:sku0C87:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 13 9340 dmi.product.sku: 0C87 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169185/+subscriptions

[Bug 2169198] Re: 26.10 mini-iso: screen hangs after selecting target

** 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/2169198 Title: 26.10 mini-iso: screen hangs after selecting target Status in linux package in Ubuntu: New Bug description: Every stonking mini-iso daily since 20260917 fails to boot. After selecting any target in the "Choose an Ubuntu version to install" menu, the screen freezes on the boot text and the machine hangs forever. The resolute mini-iso and pre-20260917 stonking dailies work. The error seems to happen in the kernel. In order to reproduce, follow the instructions here to do a mini-iso smoke test for the stonking daily: https://github.com/ubuntu/ubuntu-manual-tests/blob/main/resolute/testsuites/Ubuntu%20Mini%20ISO/Mandatory/Smoke%20Test.md The kernel log and serial output are attached. In order to get the kernel log, the mini-iso was rebuilt with `console=ttyS0 earlyprintk=serial,ttyS0,115200`appended to the kexec command line in `/scripts/casper-premount/30mini-iso-menu` and the serial output was captured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169198/+subscriptions

[Bug 2169102] Re: [Regression] Window flickering and blanking on Electron/Chromium apps under Wayland with legacy radeon driver (Radeon HD 7670M) on kernel 7.0.0-34-generic

** Attachment added: "ERROR.mp4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169102/+attachment/6004606/+files/ERROR.mp4 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169102 Title: [Regression] Window flickering and blanking on Electron/Chromium apps under Wayland with legacy radeon driver (Radeon HD 7670M) on kernel 7.0.0-34-generic Status in linux package in Ubuntu: New Bug description: Problem Description: After updating to kernel 7.0.0-34-generic, specific applications (specifically Chromium/Electron-based apps with hardware acceleration enabled) experience severe window flickering, blanking, and intermittent black screens during redraws. The desktop shell remains responsive, but the client window contents intermittently fail to present or render black frames. Hardware & Environment Information: - Host: Toshiba Satellite S855 - Kernel: 7.0.0-34-generic - Display Server: Wayland (echo $XDG_SESSION_TYPE -> wayland) - GPU: AMD/ATI Thames [Radeon HD 7500M/7600M Series] (Radeon HD 7670M) [1002:6840] (rev ff) - Subsystem: Toshiba Corporation [1179:fb22] - Active Driver: radeon (DRM 2.51.0 / KMS Turks) Relevant dmesg / DRM logs: [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (TURKS 0x1002:0x6840 0x1179:0xFB22 0x00). [drm] Detected VRAM RAM=2048M, BAR=256M [drm] Loading TURKS Microcode radeon 0000:01:00.0: [drm] PCIE GART of 1024M enabled. radeon 0000:01:00.0: [drm] fb0: radeondrmfb frame buffer device Steps to Reproduce: 1. Boot with kernel 7.0.0-34-generic into a default Wayland session. 2. Launch a hardware-accelerated application (e.g., Google Chrome, Gemini PWA/Electron, VS Code). 3. Interact with the window or hover over UI elements. 4. The window content rapidly flickers between the rendered page and solid black. Expected Behavior: Window surfaces should redraw cleanly without buffer flickering or black frames under the legacy radeon KMS driver. Observed Behavior: Window rendering intermittently collapses to a black surface during buffer swaps under Wayland. Regression: This issue was introduced with the recent kernel update. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: daby 4597 F.... wireplumber /dev/snd/controlC1: daby 4597 F.... wireplumber /dev/snd/seq: daby 4581 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 17:17:42 2026 InstallationDate: Installed on 2025-02-25 (583 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) IwDevWlp8s0Link: Not connected. MachineType: TOSHIBA Satellite S855 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-34-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: 04/15/2013 dmi.bios.release: 6.70 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.70 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 6.20 dmi.modalias: dmi:bvnInsydeCorp.:bvr6.70:bd04/15/2013:br6.70:efr6.20:svnTOSHIBA:pnSatelliteS855:pvrPSKFWU-002002:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKFWU:pfaDakar10F/FG: dmi.product.family: Dakar 10F/FG dmi.product.name: Satellite S855 dmi.product.sku: PSKFWU dmi.product.version: PSKFWU-002002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169102/+subscriptions