[Bug 2161930] Re: LG Monitor shows black screen when set to 144hz

[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161930 Title: LG Monitor shows black screen when set to 144hz Status in linux package in Ubuntu: Expired Bug description: ### Issue I have a PC connected to an LG 27GL850-B Ultragear QHD monitor. When I launch Ubuntu, the LG screen displays a black screen by default. If I change the refresh rate from 144hz to 120hz the monitor will work correctly. ### Expected behavior The monitor should be configured to display correctly by default. ### System Info * OS: Ubuntu 26.04 LTS * Hardware Model: ASUS TUF GAMING B550M-PLUS _WI-FI_ * Processor: AMD Ryzen™ 5 5600X × 12 * Graphics: zink Vulkan 1.4(NVIDIA GeForce RTX™ 4070 SUPER (NVK AD104)) * Firmware Version: 3621 * Kernel Version: Linux 7.0.0-14-generic ### XOrg version xorg: Installed: (none) Candidate: 1:7.7+26ubuntu1 Version table: 1:7.7+26ubuntu1 500 500 http://archive.ubuntu.com/ubuntu resolute/universe amd64 Packages ### Extra info * I am booting Ubuntu off an unmodified USB image in "Try Ubuntu" mode * I have two monitors connected. The 144hz LG connected via DisplayPort and a 60hz Dell connected via HDMI * The same issue occurred when booting my PC on Linux Mint ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 22:34:47 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161930/+subscriptions

[Bug 2171268] Re: [ASUS ExpertCenter / Raptor Lake] Internal speakers produce no sound (Realtek ALC256 / SOF driver)

snd_hda_intel: dmic_detect=0 snd_intel_dspcfg: dsp_driver=1 snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw ------------------------------------------ Please remove ^these customizations, and any others you've made to fix this issue, reboot and run the following command to gather relevant logs: apport-collect 2171268 ** Package changed: linux (Ubuntu) => alsa-driver (Ubuntu) ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171268 Title: [ASUS ExpertCenter / Raptor Lake] Internal speakers produce no sound (Realtek ALC256 / SOF driver) Status in alsa-driver package in Ubuntu: Incomplete Bug description: Issue Description: Internal speakers are completely silent on an ASUS ExpertCenter laptop with Intel Raptor Lake platform using the Sound Open Firmware (SOF) driver and Realtek ALC256 codec. Hardware & System Info: - Model: ASUS ExpertCenter (Intel Raptor Lake) - Audio Codec: Realtek ALC256 - OS: Ubuntu Linux 26.04 - Sound Server: PipeWire / WirePlumber - Low-level driver: snd-sof-pci-intel-tgl Verification & Troubleshooting Performed: 1. Hardware functional test: Audio and speakers operate correctly during BIOS hardware diagnostics (rules out physical hardware failure). 2. Volume / Mute checks: ALSA Mixer (`alsamixer`) and PipeWire show Master, Speaker, and PCM channels unmuted (`00`) and set to appropriate volume levels. 3. Troubleshooting attempts: - Modifying module parameters (`options snd-intel-dspcfg dsp_driver=1`) - Disabling Fast Boot in BIOS - Updating to the latest mainline kernel - Overriding pin configuration via `hdajackretask` None of these attempts produced audio output through the internal speakers. Diagnostic Log Attached: I have attached the full diagnostic output generated by `alsa-info.sh` (containing ACPI tables, pin configurations, and SOF driver dmesg logs). Request: Please review the attached alsa-info log to include the proper pin-mapping quirk/patch for this ASUS ExpertCenter model in future kernel/firmware updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2171268/+subscriptions

[Bug 2127044] Re: MT7925 wifi is hard blocked on HP's machine

** Tags added: linux-firmware-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/2127044 Title: MT7925 wifi is hard blocked on HP's machine Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-mediatek package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-firmware-mediatek source package in Noble: In Progress Status in linux-oem-6.14 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux-firmware-mediatek source package in Questing: Won't Fix Status in linux-oem-6.14 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Bug description: [Impact] The wifi is hard blocked and can't be used randomly. [Fix] The issue is introduced by commit 085749115fd37 ("wifi: mt76: mt7925: add rfkill_poll for hardware rfkill") The machine doesn't support this feature may lead to undefined behavior, and MTK will submit a firmware to fix this issue in the near feature. For short-term solution, we made a DMI quick to list the machines that doesn't support this feature. [Test] 1. Boot up HP Z2 Mini G1a Workstation 2. Run `rfkill list` to check wlan0 block state 3. Re-plug power cord and then check rfkill state again 4. The wlan0 should not be hard blocked. [Where problems could occur] Should be pretty safe to return the function call directly, since the machine doesn't support it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2127044/+subscriptions

[Bug 2171046] Re: Firmware-less serdev device returns ENODEV for modalias, breaking sysfs enumeration

** 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/2171046 Title: Firmware-less serdev device returns ENODEV for modalias, breaking sysfs enumeration Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: The Dell UART backlight driver creates a  serial0-0  serdev device without ACPI or Device Tree firmware metadata. When userspace reads its  modalias  sysfs file, serdev tries to generate an alias from ACPI and OF data; both lookups return  -ENODEV , which serdev incorrectly propagates as a read failure. The modalias should instead be readable with empty content, because this manually created device has no firmware alias. Returning  -ENODEV  makes sysfs enumeration fail and causes Checkbox  dkms_info_attachment  to abort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171046/+subscriptions

[Bug 2171271] Re: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 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/2171271 Title: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04 Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. 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/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171271/+subscriptions

[Bug 2171271] [NEW] Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04

Public bug reported: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. 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/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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/2171271 Title: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04 Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. 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/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171271/+subscriptions

[Bug 2169736] Re: RTC device disappears after updating to 7.0.0-39-generic

Thank you very much for reporting this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169736 Title: RTC device disappears after updating to 7.0.0-39-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: Issue seen on 26.04 and probably other series as well. ubuntu@dell-latitude-5411-c27717:~$ uname -a Linux dell-latitude-5411-c27717 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux ubuntu@dell-latitude-5411-c27717:~$ cat /sys/class/rtc/rtc0/since_epoch 1791307002 # Update to 7.0.0-39-generic and reboot ubuntu@dell-latitude-5411-c27717:~$ uname -a Linux dell-latitude-5411-c27717 7.0.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 24 11:18:19 UTC 2026 x86_64 GNU/Linux ubuntu@dell-latitude-5411-c27717:~$ cat /sys/class/rtc/rtc0/since_epoch cat: /sys/class/rtc/rtc0/since_epoch: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-39-generic 7.0.0-39.39 ProcVersionSignature: Ubuntu 7.0.0-39.39-generic 7.0.14 Uname: Linux 7.0.0-39-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2123 F.... wireplumber /dev/snd/seq: ubuntu 2102 F.... pipewire CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 7 01:19:33 2026 InstallationDate: Installed on 2026-05-19 (141 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlo1Link: Not connected. MachineType: Dell Inc. Latitude 5411 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-39-generic root=UUID=16b44133-d26e-466c-8e12-da20de044692 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: 05/03/2020 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd05/03/2020:br1.1:svnDellInc.:pnLatitude5411:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku09C0:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 5411 dmi.product.sku: 09C0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169736/+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

Thank you very much for reporting this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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 2169338] Re: Kernel oops / GPF in path_is_under() from complete_walk() on openat — 7.0.0-34/-38-generic and 7.0.0-1017-azure, Hyper-V Gen2 guest

Thanks a lot for your updates. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169338 Title: Kernel oops / GPF in path_is_under() from complete_walk() on openat — 7.0.0-34/-38-generic and 7.0.0-1017-azure, Hyper-V Gen2 guest Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: New Bug description: An Ubuntu 26.04.1 LTS VM on Hyper-V repeatedly oopses in path_is_under(), called from complete_walk() during openat(). The faulting address is a different garbage value each time: either fffffffffffffff0 or a non-canonical pointer. That suggests a corrupted or freed struct mount being walked through mnt_parent. With panic_on_oops=0 the task dies holding a lock, every later bubblewrap (bwrap) process soft-locks in create_user_ns -> alloc_ucounts / current_chrooted -> _raw_spin_lock, and the system wedges. With panic_on_oops=1 it panics and reboots. Reproduced on three kernel builds within ~28 hours: - 7.0.0-34-generic: 3 oopses (Comm: MainThread x2, depmod) - 7.0.0-38-generic: 1 oops (Comm: MainThread) - 7.0.0-1017-azure (7.0.14 base): 1 oops (Comm: git) == Environment == - Ubuntu 26.04.1 LTS (resolute), cloud image (ubuntu-26.04-server-cloudimg-amd64.img) - Hyper-V Gen 2 VM on Windows 11 Pro 26200, Secure Boot (MS UEFI CA), 8 vCPU, 8 GB static RAM (Dynamic Memory was enabled for the first incident; disabled since), 8 GB swapfile, ext4 root - Host CPU: Intel Core i9-14900K - kernel.apparmor_restrict_unprivileged_userns=1 (default) == Trace (7.0.0-1017-azure, representative) == Oops: general protection fault, probably for non-canonical address 0xaa72f400ffffffef: 0000 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 45217 Comm: git Not tainted 7.0.0-1017-azure #17-Ubuntu PREEMPTLAZY Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/25/2025 RIP: 0010:path_is_under+0x60/0xa0 Call Trace: complete_walk+0x9c/0xc0 do_open+0x1b3/0x400 path_openat+0x113/0x290 do_file_open+0xdf/0x1a0 do_sys_openat2+0x7a/0xe0 __x64_sys_openat+0x5f/0xa0 do_syscall_64+0x105/0x5a0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Kernel panic - not syncing: Fatal exception On -generic the first oops was "BUG: unable to handle page fault for address: fffffffffffffff0" at path_is_under+0x50/0x90 with the same call chain. == Workload / when it happens == - The VM ran cleanly for ~24h, then oopsed repeatedly once it was used as a development box: Claude Code (Node/Bun), git, pnpm, Chrome under XFCE/xrdp, and Tailscale. - Faulting tasks are ordinary file opens by unprivileged processes (MainThread = Claude Code's main thread, git) and root (depmod during a kernel package postinst). - Intervals between oopses ranged from ~1 minute to ~2 hours of uptime. == Ruled out == - Filesystem: a forced e2fsck of root was clean apart from an "extent tree could be narrower" optimisation note. - Memory pressure: it reproduces with static RAM and >5 GB free; no OOM events. - Host problems: no host errors, and a WSL2 guest on the same host is unaffected. == Possibly related == The first incident followed Hyper-V Dynamic Memory hot-add failures 6 minutes earlier: "40-vm-hotadd.rules: Failed to write 'online'" and "workqueue: hot_add_req [hv_balloon] hogged CPU". Dynamic Memory has been off since, and the oopses continue. == Attachments == - oops-all-6-crashes.txt: full oops texts from systemd-pstore (efi_pstore) for every incident - hyperv-guest-crash-events.txt: Hyper-V Worker event 18590, which includes the guest's final kmsg - system-info.txt: version_signature, uname, installed kernels, cmdline, CPU/memory, userns settings --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Oct 6 21:56 seq crw-rw---- 1 root audio 116, 33 Oct 6 21:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20260927 CloudSubPlatform: config-disk (/dev/sdb1) DistroRelease: Ubuntu 26.04 Lspci: Lspci-vt: Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux-azure (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=unknown ProcFB: 0 hyperv_drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=UUID=747687d9-c20c-41f8-bfb8-7f4a57910c51 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image resolute Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/25/2025 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 3897-2538-6803-7408-7643-1671-78 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd09/25/2025:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:skuNone:pfaVirtualMachine: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169338/+subscriptions

[Bug 2170396] Re: Lenovo Legion screen flickering on Kubuntu 26.04 (Fixed by lowering brightness / 165Hz conflict)

Trying to upload dmesg once again failed: Timeout error Sorry, something just went wrong in Launchpad. We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience. Trying again in a couple of minutes might work. If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot. (Error ID: OOPS-c4d7a1b4a813cc3750c6e2a1a0165880) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170396 Title: Lenovo Legion screen flickering on Kubuntu 26.04 (Fixed by lowering brightness / 165Hz conflict) Status in linux package in Ubuntu: New Bug description: I installed Kubuntu 26.04 on my Lenovo Legion laptop (NVIDIA graphics) and experienced severe screen flickering. Key behaviors observed: • The panel natively runs at 165.04Hz. • Forcing the refresh rate down to 60Hz via kscreen-doctor temporarily improved the flickering but did not resolve it. • Forcing "Discrete Graphics" in the BIOS resulted in a total black screen upon OS load. • Crucial Hardware Link: Lowering the screen brightness manually to 30% reduces the flickering to minimal/manageable levels, suggesting a power-delivery/backlight voltage or PWM conflict with the modern kernel's power-saving features. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jgw 1549 F.... pipewire jgw 1561 F.... wireplumber /dev/snd/controlC0: jgw 1561 F.... wireplumber /dev/snd/seq: jgw 1549 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Oct 9 19:23:43 2026 InstallationDate: Installed on 2026-10-07 (2 days ago) InstallationMedia: Kubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826.1) MachineType: LENOVO 82TF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=3ad3b9bb-66ac-4411-a956-601a55f3254c ro quiet splash pcie_aspm=off acpi_backlight=native PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2025 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: JYCN58WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 16IAH7 dmi.ec.firmware.release: 1.55 dmi.modalias: dmi:bvnLENOVO:bvrJYCN58WW:bd03/03/2025:br1.58:efr1.55:svnLENOVO:pn82TF:pvrLegionS716IAH7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegionS716IAH7:skuLENOVO_MT_82TF_BU_idea_FM_LegionS716IAH7:pfaLegionS716IAH7: dmi.product.family: Legion S7 16IAH7 dmi.product.name: 82TF dmi.product.sku: LENOVO_MT_82TF_BU_idea_FM_Legion S7 16IAH7 dmi.product.version: Legion S7 16IAH7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170396/+subscriptions

[Bug 2170917] Re: No internal microphone on AMD systems with RT712-VB SoundWire codec

** 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/2170917 Title: No internal microphone on AMD systems with RT712-VB SoundWire codec Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-7.3 package in Ubuntu: Invalid Status in linux source package in Resolute: Invalid Status in linux-oem-7.3 source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Status in linux-oem-7.3 source package in Stonking: Invalid Bug description: [Impact] On some AMD systems with an RT712-VB SoundWire codec and TAS2783 amplifiers, the internal microphone and speakers don't show up. The machine driver needed to enable them is 28114992dd2f ("ASoC: amd: acp: enable TAS2783 and add RT712-VB SoundWire machine"). That commit makes SND_SOC_AMD_LEGACY_SDW_MACH select SND_SOC_TAS2783_SDW without checking its dependencies. The codec also needs SND_SOC_SDCA andEFI. With EFI=n, the build warns: WARNING: unmet direct dependencies detected for SND_SOC_TAS2783_SDW Depends on [n]: SOUND [=m] && SND [=m] && SND_SOC [=m] && SOUNDWIRE [=m] && SND_SOC_SDCA [=m] && EFI [=n] Selected by [m]: - SND_SOC_AMD_LEGACY_SDW_MACH [=m] && ... The codec is force-enabled when its dependencies are not met. This can break builds and configs. [Fix] Two Kconfig fixes for the above commit. Both are in sound/soc/amd/acp/Kconfig. d06607bafb36 ASoC: amd: acp: fix TAS2783 SoundWire codec unmet dependencies Changes the select to "select SND_SOC_TAS2783_SDW if SND_SOC_SDCA && EFI". 4d2b92b82ee8 ASoC: amd: acp: add EFI dependency for selecting TAS2783 Makes SND_SOC_AMD_LEGACY_SDW_MACH depend on EFI. Both commits are merged upstream in the ASoC tree (Mark Brown). Neither is in a released v* tag yet. Links: https://patch.msgid.link/20260924124205.3376083-1-syed.sabakareem@amd.com https://patch.msgid.link/20260925131137.146638-1-arnd@kernel.org [Test Plan] Check the config with EFI off: $ scripts/config --disable EFI $ make olddefconfig Without patches: the "unmet direct dependencies detected for SND_SOC_TAS2783_SDW" warning shows up. With patches: no warning. On the Ubuntu config (EFI=y, SDCA=m), check the codec is still built: $ grep -E 'SND_SOC_TAS2783_SDW|SND_SOC_AMD_LEGACY_SDW_MACH' .config Both should be =m. On an affected AMD machine, check the microphone is still present: $ arecord -l The internal digital mic capture device should be listed. [Where problems could occur] Could break the AMD ACP SoundWire machine driver (snd-acp-sdw-legacy-mach) and the TAS2783 codec build. If the Kconfig conditions are wrong, the TAS2783 codec or the machine driver would not be built. The system would then have no internal microphone or speakers on the affected AMD systems. The new EFI dependency would also hide the machine driver in configs without EFI. Ubuntu kernels enable EFI, so this should not matter for them. The change only touches Kconfig. It has no runtime code change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2170917/+subscriptions

[Bug 2171020] Re: PCI/PM: Restore BARs after powering up during enumeration

** 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/2171020 Title: PCI/PM: Restore BARs after powering up during enumeration Status in linux package in Ubuntu: New Bug description: Gather the crash kernel, which hangs. This issue was reported by HPE Commit 4d4c10f763d7 ("PCI: Explicitly put devices into D0 when initializing") added pci_pm_power_up_and_verify_state() to pci_pm_init(). The helper ignores pci_power_up()'s return value indicating that BARs need restoring. Its resume callers restore saved configuration afterwards; pci_pm_init() does not. D3hot-to-D0 may reset a device and lose its BARs (PCI PM 1.2, sec 5.4.1). After enumeration powers it up, pci_enable_device() reads D0 and skips the full power-up path. Previously, a device still in D3hot at enable time took that path, including BAR restoration. On AMD Venice SP7, two AMD xHCI controllers [1022:17d2] are in runtime D3hot with No_Soft_Reset clear before kdump. Diagnostic reads on v7.3-rc6-37 show the following for 0000:01:00.4 in the crash kernel: PMCSR BAR0 before the platform power call 0003 f4100004 after the platform power call 0003 f4100004 after native D0 power-up 0000 00000004 The upper BAR DWORD stays zero. pci_power_up() returns 1, but the BAR address remains zero while dev->resource[0] still contains 0xf4100000. Without BAR restoration, the crash kernel hangs during boot. The last console output includes: pci 0000:01:00.4: enabling device (0000 -> 0002) Restoring both controllers' BARs gives matching readbacks and allows kdump to save a vmcore and reboot. An AMD Turin xHCI [1022:1557] shows the same BAR loss; restoring its BAR also allows kdump to complete. Read the initial power state first. Otherwise, pci_power_up() may request a BAR restore based on a cached PCI_UNKNOWN state, even when the device is already in D0. For devices already in D0, only synchronize the platform state so that ACPI calls such as _REG still run. For other states, use pci_set_full_power_state() to power up the device and restore BARs when needed. Impact : kdump to save a vmcore and reboot with this fix. Without it , it hangs. See description above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171020/+subscriptions

[Bug 2141741] Re: 55-initrd.install silently exits 0 when initrd missing causing undetectable kernel panic on NVMe systems

** Changed in: grub2 (Debian) Status: Unknown => New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2141741 Title: 55-initrd.install silently exits 0 when initrd missing causing undetectable kernel panic on NVMe systems Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in grub2 package in Debian: New Bug description: [ Impact ] When a kernel postinst hook fails (e.g. DKMS module build failure), the kernel package remains half-configured: vmlinuz is installed and /usr/lib/linux/triggers/<version> is present, but no matching initrd is generated. A subsequent update-grub invocation (such as during removal of an older kernel) scans /boot and generates a boot menuentry for the incomplete kernel without an initrd line. On systems where storage drivers (NVMe, SATA, SAS) are built as modules, booting this entry causes an immediate, undetectable kernel panic (VFS: Unable to mount root fs on unknown-block(0,0)). [ Fix ] In /etc/grub.d/10_linux, when inspecting a kernel where no initrd was found (test -z "${initrd_real}"), check if a pending kernel trigger marker exists in /usr/lib/linux/triggers/${version} or /usr/lib/linux/triggers/${alt_version}. If the trigger marker is present, skip generating a boot menuentry for that kernel image. This prevents update-grub from publishing unbootable kernels to grub.cfg. [ Test Plan ] 1. Simulate an incomplete kernel installation: sudo touch /boot/vmlinuz-9.9.0-test-generic sudo touch /usr/lib/linux/triggers/9.9.0-test-generic sudo rm -f /boot/initrd.img-9.9.0-test-generic 2. Run sudo update-grub. 3. Verify behavior: - Without fix: GRUB outputs "Found linux image: /boot/vmlinuz-9.9.0-test-generic" and writes a stanza lacking an initrd line. - With fix: GRUB outputs "Skipping linux image with pending post-installation trigger and no initrd: /boot/vmlinuz-9.9.0-test-generic", and no stanza is generated. 4. Clean up test files (sudo rm -f /boot/vmlinuz-9.9.0-test-generic /usr/lib/linux/triggers/9.9.0-test-generic) and verify standard installed kernels generate valid boot entries. [ Where problems could occur ] The check only triggers when both conditions are met: initrd_real is empty AND a trigger marker exists in /usr/lib/linux/triggers/. Custom kernels intentionally configured without an initrd do not have markers under /usr/lib/linux/triggers/ and continue to work as before. If a kernel postinst script fails to clean up its trigger marker after a successful run, that kernel would be skipped until the stale marker is removed. [ Other Info ] - Debian BTS bug: https://bugs.debian.org/1151014 - Development series (stonking): debdiff prepared against 2.14-2ubuntu3 (version 2.14-2ubuntu4). - Stable SRU (noble): debdiff prepared against 2.12-1ubuntu7.3 (version 2.12-1ubuntu7.4). - PPA test builds: ppa:steelf/ppa (grub2 2.14-2ubuntu4~ppa1, grub2 2.12-1ubuntu7.4~ppa1). --- [ Original Report ] ENVIRONMENT: - Ubuntu 24.04 Noble (HWE kernel) - systemd version: 255 (255.4-1ubuntu8.10) - Kernel: 6.17.0-14-generic - Storage: NVMe SSD - File: /usr/lib/kernel/install.d/55-initrd.install - Package owner: systemd (confirmed via dpkg -S) BUG: When initrd generation fails or is skipped during kernel installation, 55-initrd.install detects the missing initrd but exits 0 (success) instead of exit 1 (failure). Relevant code in 55-initrd.install (line 26): if [ -e "$INITRD_SRC" ]; then ln -fs "$INITRD_SRC" "$KERNEL_INSTALL_STAGING_AREA" else echo "$INITRD_SRC does not exist, not installing an initrd" fi exit 0 <- BUG IS HERE This silent success causes GRUB to write a boot entry for a kernel with no initrd, with zero warning to the user. HOW THIS CAUSES KERNEL PANIC: Ubuntu's kernel config has CONFIG_BLK_DEV_NVME=m meaning the NVMe storage driver exists ONLY as a module inside initramfs. Without initramfs: - NVMe driver never loads - Kernel cannot see any storage device - Results in: VFS: Unable to mount root fs on unknown-block(0,0) - KERNEL PANIC on every boot - silent, no warning given HOW I TRIGGERED THIS: virtualbox-dkms 7.0.16 (dfsg) fails to build for kernel 6.17 due to missing VBox/cdefs.h header. DKMS exits code 11. run-parts stops alphabetically - 'd' (dkms) runs before 'i' (initramfs-tools) - so initramfs is never generated. 55-initrd.install then silently exits 0 -> GRUB creates unbootable boot entry -> KERNEL PANIC on reboot. This failed silently 3 days in a row (Feb 11, 12, 13 2026) confirmed in /var/log/dpkg.log and /var/log/apt/term.log. PROPOSED FIX: Change line 26 of 55-initrd.install from: exit 0 to: exit 1 When initrd is missing, this should be a HARD FAILURE not a silent warning. This would cause apt to report the error visibly and prevent GRUB from creating an unbootable boot entry. RELATED BUG: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2136499 (virtualbox-dkms FTBFS triggers this silent failure) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2141741/+subscriptions