[Bug 1948040] Re: modprobe.d is not honored on uc20

[Expired for snapd because there has been no activity for 60 days.] ** Changed in: snapd 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/1948040 Title: modprobe.d is not honored on uc20 Status in snapd: Expired Status in linux package in Ubuntu: Invalid Bug description: Ubuntu kernels by default ship modprobe.d that excludes many modules from loading: # Kernel supplied blacklist for linux 5.4.0-89-generic amd64 # modprobe.d/common.conf # LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate blacklist snd-mixer-oss blacklist snd-pcm-oss # Autogenerated watchdog blacklist blacklist acquirewdt blacklist advantechwdt blacklist ahc1ec0-wdt blacklist alim1535_wdt blacklist alim7101_wdt blacklist cadence_wdt blacklist cpu5wdt blacklist da9052_wdt blacklist da9055_wdt blacklist da9062_wdt blacklist da9063_wdt blacklist dw_wdt blacklist ebc-c384_wdt blacklist eurotechwdt blacklist f71808e_wdt blacklist hpwdt blacklist i6300esb blacklist iTCO_vendor_support blacklist iTCO_wdt blacklist ib700wdt blacklist ibmasr blacklist ie6xx_wdt blacklist it8712f_wdt blacklist it87_wdt blacklist kempld_wdt blacklist machzwd blacklist max63xx_wdt blacklist mei_wdt blacklist mena21_wdt blacklist menf21bmc_wdt blacklist menz69_wdt blacklist mlx_wdt blacklist ni903x_wdt blacklist nic7018_wdt blacklist nv_tco blacklist of_xilinx_wdt blacklist pc87413_wdt blacklist pcwd_pci blacklist pcwd_usb blacklist pretimeout_panic blacklist rave-sp-wdt blacklist retu_wdt blacklist sbc60xxwdt blacklist sbc_epx_c3 blacklist sbc_fitpc2_wdt blacklist sc1200wdt blacklist sch311x_wdt blacklist smsc37b787_wdt blacklist softdog blacklist sp5100_tco blacklist tqmx86_wdt blacklist twl4030_wdt blacklist via_wdt blacklist w83627hf_wdt blacklist w83877f_wdt blacklist w83977f_wdt blacklist wafer5823wdt blacklist wdat_wdt blacklist wdt_pci blacklist wm831x_wdt blacklist wm8350_wdt blacklist xen_wdt blacklist ziirave_wdt However kernel snaps do not provide modprobe.d nor they are used by default. Is pc-kernel supposed to skip shipping those? Should there be modprobe.d in the core20 snap that prevents these known modules from loading by default? Also I'm not too sure about the watchdog modules exclusion, given that systemd can operate watchdogs by default, hence it shouldn't be too dangerous to autoenable them? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1948040/+subscriptions

[Bug 2172049] Re: [Huawei MDF-X] Conexant SN6140: speaker and headphone output simultaneously (SSID 19e5:3e68)

** 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/2172049 Title: [Huawei MDF-X] Conexant SN6140: speaker and headphone output simultaneously (SSID 19e5:3e68) Status in linux package in Ubuntu: New Bug description: Problem Description: On Huawei MateBook MDF-X with Conexant SN6140 codec, when headphones are plugged into the 3.5mm jack, audio continues to play from both the internal speakers and the headphones simultaneously. No independent "Headphone" output port is selectable in pavucontrol. Hardware Information: - Laptop Model: Huawei MDF-X - Audio Controller: Intel Alder Lake PCH-P [8086:51c8] - Subsystem SSID: 19e5:3e68 - Codec: Conexant SN6140 - Kernel driver in use: sof-audio-pci-intel-tgl - OS: Ubuntu 26.04 - Kernel: 7.0.0-38-generic Relevant lspci -nv output: 00:1f.3 0401: 8086:51c8 (rev 01) Subsystem: 19e5:3e68 Kernel driver in use: sof-audio-pci-intel-tgl Analysis: The existing kernel quirk for Huawei MateBook 14 with SN6140 targets PCI SSID 19e5:329e (CXT_FIXUP_MATEBOOK14_SN6140). This machine has SSID 19e5:3e68, so that quirk does not match. The hardware behaviour is the same: speaker pin 0x17 follows headphone pin 0x16, causing simultaneous output. Request: Please add a SND_PCI_QUIRK for 0x19e5, 0x3e68 to apply the same SN6140 routing fix used for 19e5:329e, or extend the existing quirk to cover this SSID. Attachments: Full lspci -nv output has been provided. Additional dmesg and codec info can be collected via ubuntu-bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172049/+subscriptions

[Bug 2172089] Re: SD card hotplug detection broken on GL9750 (17a0:9750) with kernel 7.0.0-38, works on 7.0.0-34

** 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/2172089 Title: SD card hotplug detection broken on GL9750 (17a0:9750) with kernel 7.0.0-38, works on 7.0.0-34 Status in linux package in Ubuntu: New Bug description: SD card hotplug detection broken on GL9750 (17a0:9750) with kernel 7.0.0-38, works on 7.0.0-34 Summary On a Lenovo ThinkPad T14 Gen 2i, the internal SD card reader (Genesys Logic GL9750, 17a0:9750, driver sdhci-pci) stops detecting SD card insertion/removal with kernel 7.0.0-38-generic (Ubuntu 26.04.1). The card is only detected: at boot, if it is already inserted, or after manually reloading the driver (modprobe -r sdhci_pci && modprobe sdhci_pci). Hotplug (insert/remove while the system is running) does not work: no interrupt, no mmc0: new ... card message, no mmcblk0 device, and the mmc0 IRQ count does not change. The same hardware works correctly on kernel 7.0.0-34-generic and on Ubuntu 24.04.4. This looks like a regression introduced between 7.0.0-34 and 7.0.0-38 in the MMC subsystem. Environment Machine: Lenovo ThinkPad T14 Gen 2i, model 20W1S4AR3A BIOS: N34ET72W (1.72) OS: Ubuntu 26.04.1 LTS Kernel (broken): 7.0.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 4 09:10:14 UTC 2026 x86_64 Kernel (working): 7.0.0-34-generic SD host controller: 0a:00.0 SD Host controller [0805]: Genesys Logic, Inc GL9750 SD Host Controller [17a0:9750] (rev 01) Subsystem: Lenovo 17aa:22c9 Driver: sdhci-pci (modules: sdhci_pci, sdhci_uhs2, sdhci, cqhci) Cards tested: SanDisk/Genesys-class SDXC 64 GB (SC64G, 59.5 GiB), 128 GB (SC128, 119 GiB), 64 GB (EC2QT, 59.6 GiB); exFAT and FAT32, MBR partition tables. Steps to reproduce Boot kernel 7.0.0-38-generic with no card in the internal reader. Insert an SD card into the internal reader. Wait several seconds. Observed: Code block $ ls /sys/bus/mmc/devices/ # empty $ ls /sys/block/ | grep mmc # empty $ grep mmc0 /proc/interrupts 179: 0 0 28 0 0 0 0 0 IR-PCI-MSI-0000:0a:00.0 0-edge mmc0 No new line in dmesg / journalctl -k. Reload the driver: Code block sudo modprobe -r sdhci_pci && sudo modprobe sdhci_pci The card is then detected immediately: Code block mmc0: SDHCI controller on PCI [0000:0a:00.0] using ADMA mmc0: new UHS-I speed SDR104 SDXC card at address aaaa mmcblk0: mmc0:aaaa SC128 119 GiB Expected behaviour The card should be detected on insertion without reloading the driver, as it is on kernel 7.0.0-34 and on Ubuntu 24.04.4. Additional data Module source versions (34 vs 38) srcversion identifies the source revision of each module. It is identical for the SDHCI drivers in both kernels, and only changed for mmc_block (mmc_core is built-in and therefore not comparable as a module): module 7.0.0-34 7.0.0-38 changed sdhci DAA9A9704C8FBF55F4D05DB DAA9A9704C8FBF55F4D05DB no sdhci-pci C1A1864969529CEE6735087 C1A1864969529CEE6735087 no sdhci-acpi 6A7A844258E93CAD6419F39 6A7A844258E93CAD6419F39 no mmc_block DEAE47CB652E722CA4FEE53 EAF8EBAD83EEDA1E06FAEEE yes mmc_core built-in built-in n/a This suggests the regression is not in the GL9750-specific code (sdhci-pci-gli.c) but in the MMC core / block layer changes that landed in 7.0.0-38. Workarounds tried sdhci.debug_quirks=0x80 (SDHCI_QUIRK_BROKEN_CARD_DETECTION): the module loads the quirk (/sys/module/sdhci/parameters/debug_quirks = 128) and the card is detected after a reload, but hotplug still does not work. Reloading the driver always works, which is the current workaround. Other messages seen (possibly unrelated) Code block mmc0: Card is consuming too much power! mmc0: Tuning timeout, falling back to fixed sampling clock mmc0: tried to HW reset card, got error -2 pci 0000:00:1c.7: mask Replay Timer Timeout Correctable Errors due to 0000:0a:00.0 hardware defect The first three were observed with one particular card (EC2QT) that later became unresponsive; they are included for completeness. Request Please bisect the MMC changes between 7.0.0-34 and 7.0.0-38, or point to the commit that may affect card-detect handling for sdhci-pci devices that rely on the controller's internal card-present state. I can test patches or provide further logs on request. 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 23 23:35:37 2026 InstallationDate: Installed on 2026-05-29 (147 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: LENOVO 20W1S4AR3A ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: root=UUID=c2cf1c6a-75c0-4f8f-b900-157983acb240 ro quiet splash vt.handoff=7 loglevel=3 initrd=boot\initrd.img-7.0.0-38-generic SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-09 (14 days ago) dmi.bios.date: 08/31/2026 dmi.bios.release: 1.72 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET72W (1.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W1S4AR3A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrN34ET72W(1.72):bd08/31/2026:br1.72:efr1.46:svnLENOVO:pn20W1S4AR3A:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W1S4AR3A:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W1_BU_Think_FM_ThinkPadT14Gen2i:pfaThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W1S4AR3A dmi.product.sku: LENOVO_MT_20W1_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172089/+subscriptions

[Bug 2171341] Re: amdgpu: brief display noise flashes with kernel 7.0.0-38, regression from 7.0.0-34

Hi, This sounds similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181 so try the test kernel available there. If that fixes the problem for you I'll mark this report as a duplicate. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ross Porter (rossporter506) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171341 Title: amdgpu: brief display noise flashes with kernel 7.0.0-38, regression from 7.0.0-34 Status in linux package in Ubuntu: New Bug description: Since updating to kernel 7.0.0-38-generic, the display shows brief flashes of noise (roughly 0.1 seconds or shorter). The issue is not present with kernel 7.0.0-34-generic. Regression confirmed by booting between the two kernels on identical hardware and configuration: 7.0.0-34 is clean, 7.0.0-38 exhibits the noise flashes. Hardware: Slimbook EVO 14 GPU: AMD Strix [Radeon 880M OS: Slimbook OS 26 (based on Ubuntu 26.04 LTS), stock Ubuntu kernel via linux-image-generic-hwe-26.04 track (7.0.0-38.38 from the standard Ubuntu archive) Happy to attach full dmesg/journalctl output from a 7.0.0-38 session; currently booted into 7.0.0-34 as a workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171341/+subscriptions

[Bug 2171921] Re: Bluetooth HFP microphone extremely quiet on Intel Wireless 8260; kernel reports corrupted SCO packets and unknown SCO connection handle 257

** 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/2171921 Title: Bluetooth HFP microphone extremely quiet on Intel Wireless 8260; kernel reports corrupted SCO packets and unknown SCO connection handle 257 Status in linux package in Ubuntu: New Bug description: **Title:** Bluetooth HFP microphone extremely quiet on Intel Wireless 8260; kernel reports corrupted SCO packets and unknown SCO connection handle 257 ### System - OS: Ubuntu 26.04.1 - Kernel tested: `7.0.0-34-generic` and `7.0.0-38-generic` - Bluetooth controller: Intel Wireless 8260, PCI ID `8086:24f3`, revision `3a` - Bluetooth driver modules: `btusb`, `btintel`, `bluetooth` - BlueZ: `5.85-4ubuntu0.4` - PipeWire: `1.6.2` - WirePlumber: `0.5.13` - Firmware package: `linux-firmware-intel-wireless` - Controller firmware reports: `Firmware revision 0.0 build 14 week 44 2021` - Headset: Bowers & Wilkins Px8 ### Problem The Px8 microphone works normally when paired with a smartphone, but its microphone input is extremely quiet on Ubuntu. Bluetooth playback works normally. The issue is reproducible with direct PipeWire recording and is not limited to a particular speech-recognition application. ### Measurements Using `ffmpeg`'s `volumedetect` filter on recorded WAV files: - Px8 HFP/mSBC recording: mean volume between approximately `-50.4 dB` and `-55.0 dB`; latest peak `-23.5 dB`. - Internal laptop microphone: mean volume approximately `-4.2 dB` to `-9.2 dB`. Switching between mSBC and CVSD did not materially improve the Px8 microphone level. Disconnecting and reconnecting the headset also did not solve the issue. The Bluetooth input source was not muted and its configured volume was approximately 96%. ### Kernel messages during microphone recording The following messages appeared while recording from the Px8 microphone: Bluetooth: hci0: corrupted SCO packet Bluetooth: hci0: SCO packet for unknown connection handle 257 The `corrupted SCO packet` message appeared repeatedly. The unknown- connection-handle message appeared twice in the captured excerpt. ### Troubleshooting already performed - Confirmed that the headset microphone works normally with a smartphone. - Tested both `headset-head-unit` (mSBC) and `headset-head-unit-cvsd` (CVSD). - Measured recordings directly with PipeWire rather than relying only on the GNOME input meter. - Reconnected the headset and repeated the recording test. - Confirmed that PipeWire and WirePlumber were running. - Tested kernels `7.0.0-34-generic` and `7.0.0-38-generic`. - Confirmed that the `btusb` and `btintel` kernel modules are loaded. - Checked that `/usr/lib/firmware/intel/ibt-11-5.ddc.zst` and `/usr/lib/firmware/intel/ibt-11-5.sfi.zst` exist and belong to `linux-firmware-intel-wireless`. - No firmware files have been manually modified. ### Related reports Two upstream reports describe similar SCO transport symptoms: 1. An Intel AX201/AX211 report describes `SCO packet for unknown connection handle 257` after HFP profile changes, in a particular Linux/WirePlumber version combination. 2. A WirePlumber report describes corrupted SCO packets and an unknown connection handle with Bluetooth HFP audio failures. The hardware and software versions differ from this report, so the underlying cause may not be the same. ### Questions 1. Do the SCO errors indicate a Bluetooth controller/firmware problem, a Linux Bluetooth SCO connection-state issue, or an interaction with PipeWire/WirePlumber? 2. Is there a known fix applicable to Intel Wireless 8260 controllers? 3. Would an HCI snoop trace or additional kernel diagnostics help distinguish a firmware problem from a SCO connection-state problem? 4. Is there a recommended regression test for the Intel 8260 with Ubuntu 26.04 and kernel 7.0? ## 1. System configuration - Operating system: Ubuntu 26.04.1 - Laptop: ThinkPad T460 - Kernel versions tested: `7.0.0-34-generic` and `7.0.0-38-generic` - Bluetooth/WLAN adapter: Intel Wireless 8260 - PCI ID: `8086:24f3`, revision `3a` - Bluetooth kernel modules loaded: `btusb`, `btintel`, `bluetooth` - BlueZ: `5.85-4ubuntu0.4` - PipeWire: `1.6.2` - WirePlumber: `0.5.13` - Headset: Bowers & Wilkins Px8 - Intel Bluetooth firmware reported by the kernel: `Firmware revision 0.0 build 14 week 44 2021` - Firmware package: `linux-firmware-intel-wireless` - Relevant firmware files present: - `/usr/lib/firmware/intel/ibt-11-5.ddc.zst` - `/usr/lib/firmware/intel/ibt-11-5.sfi.zst` ## 2. Problem description The Bowers & Wilkins Px8 microphone works normally when connected to a smartphone. On Ubuntu, Bluetooth playback works, but the headset microphone input is extremely quiet. The problem is reproducible in direct PipeWire recordings. The internal laptop microphone records at a much higher level. The issue persists after reconnecting the headset and after switching between the mSBC and CVSD headset profiles. ## 3. Recording measurements Measurements were obtained from WAV recordings using FFmpeg's `volumedetect` filter. | Recording source/profile | Mean volume | Peak volume | |---|---:|---:| | Px8, mSBC | -50.4 dB | -27.6 dB | | Px8, mSBC | -52.6 dB | -27.1 dB | | Px8, mSBC, after reconnecting | -55.0 dB | -23.5 dB | | Px8, CVSD | -49.2 dB | -31.0 dB | | Internal microphone, recording 1 | -9.2 dB | 0.0 dB | | Internal microphone, recording 2 | -4.2 dB | 0.0 dB | The headset input is therefore approximately 40–50 dB lower in mean volume than the internal microphone in the recorded samples. The measurements depend on the speech and recording conditions, but the difference is substantial. The Px8 PipeWire input source was not muted. Its configured source volume was approximately 96% (`-1.19 dB`). ## 4. Kernel messages observed during microphone recording The following messages appeared during an active recording test: Bluetooth: hci0: corrupted SCO packet The message appeared repeatedly. The following message also appeared: Bluetooth: hci0: SCO packet for unknown connection handle 257 This appeared twice in the captured excerpt. These messages occurred while testing the Px8 microphone. Their causal relationship to the low recording level has not yet been established. ## 5. Troubleshooting already performed 1. Confirmed that the Px8 microphone works normally with a smartphone. 2. Confirmed that Bluetooth audio playback works on Ubuntu. 3. Compared the headset microphone with the internal laptop microphone. 4. Recorded microphone samples directly through PipeWire and measured their levels using FFmpeg. 5. Tested the `headset-head-unit` profile using mSBC at 16 kHz. 6. Tested the `headset-head-unit-cvsd` profile using CVSD at 8 kHz. 7. Neither profile produced a material improvement in microphone level. 8. Disconnected and reconnected the headset, then repeated the recording test. 9. Confirmed that PipeWire and WirePlumber were running. 10. Confirmed that the Bluetooth input source was not muted and was set to approximately 96% volume. 11. Tested kernels `7.0.0-34-generic` and `7.0.0-38-generic`. The microphone issue was still observed with both, although the tests were not fully controlled under identical conditions. 12. Confirmed that the `btusb`, `btintel` and `bluetooth` kernel modules were loaded. 13. Checked the USB runtime power-management setting for the Bluetooth device and temporarily set it to `on`. This did not resolve the microphone issue. 14. Confirmed that the firmware files `ibt-11-5.ddc.zst` and `ibt-11-5.sfi.zst` are installed and belong to the Ubuntu package `linux-firmware-intel-wireless`. 15. Checked the kernel log for firmware-related messages. The available excerpt reported firmware build 14, week 44 of 2021; no confirmed DDC loading error was identified in that excerpt. 16. Checked the installed firmware file's SHA-256 hash. No authoritative comparison has yet established whether the file is defective. ## 6. Questions for Ubuntu kernel/Bluetooth maintainers 1. Can the repeated `corrupted SCO packet` and `SCO packet for unknown connection handle 257` messages indicate a known Intel Bluetooth controller, firmware, or SCO connection-state problem? 2. Is there a known issue affecting Intel Wireless 8260 controllers on Ubuntu 26.04 or Linux kernel 7.0? 3. Could this issue cause an extremely low microphone recording level without completely disabling HFP audio? 4. Would an HCI snoop trace or additional kernel diagnostics help determine whether the SCO transport is corrupted or the connection state becomes inconsistent? 5. Is there a recommended regression test or a known fix for this hardware/software combination? 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: ulrich 3400 F.... wireplumber /dev/snd/seq: ulrich 3381 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 11:56:01 2026 HibernationDevice: RESUME=UUID=5a99a614-ef51-4b2f-9b3c-f73d23cfd8d6 InstallationDate: Installed on 2016-07-22 (3744 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor Bus 001 Device 004: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: LENOVO 20FMS03600 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-09-29 (23 days ago) dmi.bios.date: 03/23/2016 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET36W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS03600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrR06ET36W(1.10):bd03/23/2016:br1.10:efr1.8:svnLENOVO:pn20FMS03600:pvrThinkPadT460:rvnLENOVO:rn20FMS03600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FM_BU_Think_FM_ThinkPadT460:pfaThinkPadT460: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS03600 dmi.product.sku: LENOVO_MT_20FM_BU_Think_FM_ThinkPad T460 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171921/+subscriptions

[Bug 2171924] Re: [Dell XPS 13 9320] IPU6 MIPI camera (OV01A10 via IVSC/USB-LJCA) broken after hibernation: "mei-csi probed without device fwnode", only reboot recovers

** 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/2171924 Title: [Dell XPS 13 9320] IPU6 MIPI camera (OV01A10 via IVSC/USB-LJCA) broken after hibernation: "mei-csi probed without device fwnode", only reboot recovers Status in linux package in Ubuntu: New Bug description: Hardware: Dell XPS 13 9320 (Alder Lake), MIPI camera OV01A10 behind Intel IPU6, IVSC (mei_vsc, ivsc_csi, ivsc_ace) and USB-LJCA bridge. OS: Ubuntu 26.04, kernel 7.0.0-38-generic, BIOS 2.32.0. Camera userspace: Ubuntu IPU6 camera HAL + v4l2-relayd (v4l2loopback). Steps to reproduce: 1. Boot; the camera works (ffplay /dev/video0 shows an image, LED on). 2. systemctl hibernate, then resume. 3. Open the camera: black frames, camera LED stays off. Expected: the camera works after resume from hibernation, as it does after a normal boot. Actual: on resume, dmesg shows the sensor being removed (call traces in ov01a10_power_off() called from ov01a10_remove()), the IVSC being re-initialised ("intel_vsc intel_vsc: silicon stepping version is 0:2"), and then: ivsc_csi intel_vsc-92335fcf-...: mei-csi probed without device fwnode! After this, the sensor is missing from the media graph (media-ctl -p -d /dev/media0 shows no ov01a10 entity) and the camera HAL falls back to a generic sensor configuration (loads AR0234_TGL_10bits.aiqb instead of ov01a10.aiqb), failing with "Stream config is not supported" or waitFrame timeouts. Recovery attempts that do NOT work (relay service stopped first): - reloading intel_ipu6 / intel_ipu6_isys / intel_ipu6_psys only; - additionally reloading ov01a10, ivsc_csi, ivsc_ace, ipu_bridge (with intel_ipu6 loaded before ivsc_csi and ov01a10); - reloading the full chain: usb_ljca, gpio_ljca, i2c_ljca, spi_ljca, intel_skl_int3472_discrete, mei_vsc_hw, mei_vsc, ivsc_ace, intel_ipu6, ivsc_csi, ov01a10, isys, psys. In every case "mei-csi probed without device fwnode!" reappears and only a reboot restores the camera. Possible cause (hypothesis): on restore from hibernation the USB-LJCA device is unbound and re-bound instead of being resumed, so the IVSC and sensor devices are recreated after ipu_bridge has assigned the software fwnode graph, and that graph is not rebuilt for the new devices. Suspend-to-idle (s2idle) does not trigger this problem. 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: vittorio 6322 F.... pipewire vittorio 6332 F.... wireplumber /dev/snd/seq: vittorio 6322 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Oct 22 12:26:48 2026 HibernationDevice: RESUME=UUID=c858e7ff-beb9-4bc7-89b3-dfe8c0d001d5 InstallationDate: Installed on 2023-07-04 (1206 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. XPS 9320 ProcEnviron: LANG=it_IT.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-38-generic root=UUID=c858e7ff-beb9-4bc7-89b3-dfe8c0d001d5 ro quiet splash resume=UUID=c858e7ff-beb9-4bc7-89b3-dfe8c0d001d5 resume_offset=116736 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-07 (15 days ago) dmi.bios.date: 07/23/2026 dmi.bios.release: 2.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.32.0 dmi.board.name: 07608N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnDellInc.:bvr2.32.0:bd07/23/2026:br2.32:efr1.17:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn07608N:rvrA00:cvnDellInc.:ct10:cvr:sku0C10:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0C10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171924/+subscriptions

[Bug 2171947] Re: 6.8.0-147 regression: massively increased frequency of ACPI [ECMX] EC-mutex deadlock on HP EliteBook 860 G10 (AC._PSR), -146 unaffected

** 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/2171947 Title: 6.8.0-147 regression: massively increased frequency of ACPI [ECMX] EC- mutex deadlock on HP EliteBook 860 G10 (AC._PSR), -146 unaffected Status in linux package in Ubuntu: New Bug description: ## Summary Kernel 6.8.0-147 (noble, installed 2026-10-13) introduced a severe regression in how often a latent HP firmware ACPI Embedded-Controller mutex bug is triggered on an HP EliteBook 860 G10. On 6.8.0-146 the deadlock occurs roughly once every few days; on 6.8.0-147 it occurs multiple times per day, sometimes within ~10 minutes of boot, hard-locking systemd (PID 1) and requiring SysRq REISUB. Reverting to 6.8.0-146 restores normal (rare deadlock) behaviour. ## Hardware - HP EliteBook 860 16 inch G10 Notebook PC - BIOS: HP V70 Ver. 01.12.00, 2026-02-04 (latest available) - CPU: Intel (Raptor Lake), i915 integrated graphics ## Root cause vs regression - Root cause is an HP firmware/AML bug: a thread acquires the ACPI `[ECMX]` Embedded-Controller mutex via `\_SB.AC._PSR` (AC-adapter power-source read) and never releases it. This is HP's to fix and is not kernel-introduced. - The REGRESSION is that 6.8.0-147 triggers this firmware race far more often than 6.8.0-146, turning a rare annoyance into an unusable machine. ## Log signature (at moment of each deadlock) kernel: ACPI Error: Thread <A> cannot release Mutex [ECMX] acquired by thread <B> (20230628/exmutex-378) kernel: ACPI: \_SB_.AC__: Error reading AC Adapter state: AE_AML_NOT_OWNER Followed by hung EC event processing, then thermald/upowerd/kworker hangs, then systemd PID 1 hang and total D-Bus service-activation failure. ## Regression range - Good: 6.8.0-146 (and earlier: -139, -138, -137). Rare deadlocks (days apart). - Bad: 6.8.0-147. Frequent deadlocks (multiple per day). - -147 is stable patchset LP: #2168026. ## Suspected commits (not bisected) 1. PRIME: "ACPI: AC: Properly notify power management core about changes" — hits the exact AC._PSR path that grabs [ECMX]; plausibly increases _PSR evaluation frequency. 2. cpuidle menu governor cluster ("Remove iowait influence", "Select polling state in some more cases", plus a mid-series revert) — alters CPU idle/wake timing and hence EC poll frequency. 3. ACPICA lock/opregion changes (evxfregn ContextMutex, "Allow to skip Global Lock initialization", acpi_ev_address_space_dispatch NULL-deref, acpi_execute_reg_methods depth arg) — touch EC opregion/mutex machinery. ## Requested outcome Given the root cause is HP firmware, a DMI-based quirk for this model (EliteBook 860 G10) that restores -146 AC-notify / idle behaviour, or a revert of the offending change on affected hardware, would fix this for all affected users. ## Reproduction Boot 6.8.0-147 on an affected machine and use normally; deadlock typically occurs within minutes to a couple of hours. Does not occur (or very rarely) on 6.8.0-146. ## Workaround in place Pinned GRUB default to 6.8.0-146. ## Attachments (single archive: ecmx-bug-report.tar.gz) Required by the kernel bug template: - version.log (/proc/version_signature — note: shows -146, the GOOD kernel, as that is what is currently booted; -147 is the bad one, see "Regression range" above) - lspci-vnvn.log (sudo lspci -vnvn, full) Supporting evidence: - system-info.txt (model, BIOS, installed kernels, running kernel) - cmdline.txt (/proc/cmdline) - cpuinfo.txt (/proc/cpuinfo) - dmesg-boot-minus5-full.txt (full kernel log from a deadlock boot) - ecmx-logs-boot-minus5.txt (ECMX + AC._PSR + AE_AML_NOT_OWNER signatures) - ecmx-logs-boot-minus8.txt (same, a second deadlock boot) - acpi-tables/ (DSDT, SSDT1-29, FACP — raw ACPI tables containing the _PSR/[ECMX] AML; verified free of serial number / UUID) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171947/+subscriptions

[Bug 2171312] Re: amdgpu: horizontal screen corruption on RX 9070 XT at 4K 120/160Hz (DSC) with 7.0.0-38; 7.0.0-34 is fine

*** This bug is a duplicate of bug 2169181 *** https://bugs.launchpad.net/bugs/2169181 Hi, This looks similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181 so I will mark this as a duplicate. Let me know if you think this isn't the case. ** This bug has been marked a duplicate of bug 2169181 Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171312 Title: amdgpu: horizontal screen corruption on RX 9070 XT at 4K 120/160Hz (DSC) with 7.0.0-38; 7.0.0-34 is fine Status in linux package in Ubuntu: New Bug description: Disclaimer: this bug report was co-authoured with Claude code with assistance in finding the cause. Package: linux-image-7.0.0-38-generic (7.0.0-38.38) Regression from: linux-image-7.0.0-34-generic (7.0.0-34.34), which works correctly Release: Ubuntu 26.04 (resolute) SUMMARY After upgrading from 7.0.0-34 to 7.0.0-38, horizontal band artifacts appear across the screen whenever a large part of the display changes, for example GNOME overview and workspace transitions, or the KDE Plasma logout fade. Booting 7.0.0-34 with no other changes makes the problem disappear. HARDWARE - GPU: AMD Radeon RX 9070 XT (Navi 48, 1002:7550), Sapphire, driver amdgpu - Monitor: MSI MPG 274U E16M, 3840x2160, connected over DisplayPort (DP-2) - Mode: 3840x2160 at 160Hz (also affected at 120Hz). 60Hz is clean. - Mesa 26.0.8, linux-firmware 20260319 (both unchanged between the working and broken kernels) SOFTWARE - GNOME Shell 50.1 on Wayland (Mutter), 1.25x fractional scaling - KDE Plasma Wayland session also tested (see below) DISPLAY LINK STATE (7.0.0-38, from /sys/kernel/debug/dri/1/DP-2/) - dsc_clock_en: 1 (DSC active) - dsc_slice_width: 480 - dsc_bits_per_pixel: 256 (16 bpp) - link_settings: 4 lanes, rate 0x1e (HBR3), full speed, no link-training downgrade SYMPTOMS - Horizontal bands of corruption spanning the screen during full-screen animations. - Not seen in fullscreen games. - Not seen at 60Hz (which does not need DSC). - Reproduces in both GNOME and KDE Plasma, so it is not compositor-specific. KEY FINDING With power_dpm_force_performance_level=auto the memory clock idles at 96 MHz (pp_dpm_mclk level 0) and the artifacts appear. With echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level the artifacts disappear in both GNOME and KDE. Switching back to auto brings them back. This suggests memory clock switching is not completing within the vblank window on this DSC mode, which does not happen on 7.0.0-34. REPRODUCE 1. Boot 7.0.0-38 with the 4K 160Hz monitor on DisplayPort. 2. Leave the performance level on auto and let the GPU idle. 3. Open the GNOME overview or switch workspaces. POSSIBLE CAUSES (from comparing the 7.0.0-34 and 7.0.0-38 changelogs; I have not read the diffs or bisected) - drm/amd/display: consolidate DCN vblank/flip handling onto vupdate_no_lock - drm/amd/display: Fix DTB DTO updates breaking live pixel rate sources - drm/amd/display: ISM (idle state manager) fixes - drm/amdgpu: Fix context pstate override handling WORKAROUNDS - Boot 7.0.0-34. - Force power_dpm_force_performance_level=high. - Use 60Hz. 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: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Oct 18 02:53:09 2026 InstallationDate: Installed on 2023-06-15 (1220 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IwDevWlp5s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 amdgpudrmfb 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-04-24 (177 days ago) dmi.bios.date: 01/04/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F35 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF35:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171312/+subscriptions

[Bug 2170784] Re: Kernel 7.0.0-38 - Visual artifacts

*** This bug is a duplicate of bug 2169181 *** https://bugs.launchpad.net/bugs/2169181 Hi, This looks very similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169181 so I'll mark this as a duplicate. Let me know if you think otherwise. ** This bug has been marked a duplicate of bug 2169181 Visual background flickering and pixel artifacts after updating to kernel 7.0.0-38 (regression from 7.0.0-34) | Ubuntu 26.04 | AMD Radeon RX 9060 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170784 Title: Kernel 7.0.0-38 - Visual artifacts Status in linux package in Ubuntu: New Bug description: When running kernel 7.0.0-38 in my kubuntu system I get visual artifacts all over the place. 7.0.0-34 is fine, 7.0.0-38 causes screen artifacts, I have an RX 9070. Artifacts show randomly, but most clearly show if I move the screen brightness slider, I have HDR on. 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 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 14 09:04:24 2026 InstallationDate: Installed on 2026-06-29 (107 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp9s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. B850 AORUS ELITE WIFI7 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-34-generic root=UUID=ec0ead81-c8a1-4d73-b876-41539625716b ro quiet splash 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: 06/30/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F12b dmi.board.asset.tag: Default string dmi.board.name: B850 AORUS ELITE WIFI7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF12b:bd06/30/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnB850AORUSELITEWIFI7:pvrDefaultstring-WCP-ADO:rvnGigabyteTechnologyCo.,Ltd.:rnB850AORUSELITEWIFI7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB850MB: dmi.product.family: B850 MB dmi.product.name: B850 AORUS ELITE WIFI7 dmi.product.sku: Default string dmi.product.version: Default string-WCP-ADO dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170784/+subscriptions

[Bug 2171415] Re: [Regression] Intel H97 SATA I/O errors and DMAR faults with kernel 7.0, avoided by libata.force=max_sec=2560

I found a similar bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166838 They mention a test kernel 7.0.0-42 which is available from this PPA: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed2 Can you please test this kernel and see if this fixes the issue? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171415 Title: [Regression] Intel H97 SATA I/O errors and DMAR faults with kernel 7.0, avoided by libata.force=max_sec=2560 Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: SUMMARY Ubuntu 26.04 (kernel 7.0.0-30-generic) causes reproducible SATA I/O errors and data corruption on Gigabyte GA-H97-D3H motherboards. The problem disappears when limiting the maximum I/O request size using libata.force=max_sec=2560. HARDWARE Motherboard: Gigabyte GA-H97-D3H, BIOS F5 SATA controller: Intel H97 AHCI (8086:8c82), driver ahci SSD: Crucial MX100 256 GB (also reproduced with Samsung 870 EVO) Filesystem: ext4 on LVM on LUKS REPRODUCTION Boot Ubuntu 26.04 with kernel 7.0.0-30-generic (default parameters). On a disposable ext4 filesystem mounted at /target, run: fio --name=installer-like --filename=/target/var/tmp/fio-test.bin --rw=write --bs=4M --ioengine=sync --direct=0 --size=16G --fsync=16 --end_fsync=1 --group_reporting A/B TEST RESULTS Without workaround: max_sectors_kb = 4096 FAIL after 128 MiB (5.7 seconds) fio reports EIO during fsync. Kernel reports Intel DMAR/IOMMU faults for PCI device 00:1f.2, followed by SATA ICRC/handshake errors, failed WRITE FPDMA QUEUED commands and ext4 I/O errors. SMART UDMA_CRC_Error_Count increased from 37 to 44. With libata.force=max_sec=2560: max_sectors_kb = 1280 PASS: 16 GiB written in 84.7 seconds, no I/O errors. Both tests used the same kernel, hardware, filesystem and fio command. ADDITIONAL OBSERVATIONS - Ubuntu 26.04 installation repeatedly fails on this hardware without the workaround, but completes successfully with it. - Reproduced on three identical Gigabyte motherboards, using different SSDs, SATA cables and power supplies. - Ubuntu 24.04 with kernel 6.8 installs successfully. - Large direct-I/O fio and sequential dd tests did not reproduce the error. - The failing kernel log shows 4 MiB ATA DMA writes and DMAR faults immediately preceding SATA errors. The results suggest a regression involving large I/O requests and possibly Intel IOMMU/DMA mapping. Full dmesg, SMART, lspci and fio logs for both test configurations are attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171415/+subscriptions

[Bug 2171601] Re: Resolute update: upstream stable patchset 2026-10-21

** 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/2171601 Title: Resolute update: upstream stable patchset 2026-10-21 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2026-10-21 Ported from the following upstream stable releases: v6.18.57, v7.2.11 from git://git.kernel.org/ bnxt_en: fix DMA mapping length for padded small packets fs: Free any excess xarray nodes in clear_inode() net/mlx5e: Prevent stale XSK buffer release on refill retry net/mlx5e: Prevent stale XSK buffer release on MPWQE refill retry net: mana: check xdp_rxq registration before unreg in mana_destroy_rxq() net: mana: Skip WQ object destruction for uninitialized RXQ accel/amdxdna: Bound the sync_bo flush range to the BO size net: dsa: mt7530: fix .get_stats64 sleeping in atomic context ipv6: Fix redirect exception creation for UDP/RAW sockets ipv4: validate checksum_start before completing checksum rust_binder: reschedule node refcount update on thread exit ipv4: stop PMTU walk when nexthop group shrinks ipv4: stop exception dump when nexthop group shrinks ipv4: stop route notification sizing when nexthop group shrinks ipv4: do not warn on route notification size race ipv6: do not warn on route notification size race Input: ati_remote2 - fix type confusion in device attribute handlers Input: xpad - add support for 8BitDo Pro 2 Wired Controller for Xbox Input: xpad - add support for Corsair Novablade Pro ALSA: ctxfi: Fix memory leakage when clearing DAO input mappers ALSA: hda/tas2781: Accept V1 calibration data without CRC arm64: irq: exclude the softirq stack switch from KCOV ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode() cgroup/cpuset: Handle cpu hotplug race in guarantee_active_cpus() cipso: adjust cached option offsets when removing CIPSO dm ioctl: don't let data_start run past the buffer usb: f81604: fix struct f81604_int_data size mismatch vsock/virtio: account only unread bytes in read_skb() wifi: brcmfmac: fix P2P device removal race in brcmf_detach() wifi: mt76: mt7603: initialize global station WCID wifi: mt76: mt7996: fix uninitialized buf read in mt7996_variant_fem_init() wireguard: queueing: preserve tstamp_type when encapsulating packet wireguard: noise: reject response consumption after intermediate initiation workqueue: Fix NULL current_pwq deref in chained work check xen/netfront: don't leak the skb when xennet_fill_frags() fails tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() strparser: make sure __strp_recv isn't running before tearing down the parser swiotlb: fix default_swiotlb_limit() for non-growable default pool tcp: reject net_iov in zerocopy receive mapping hints tipc: destroy topsrv workqueues before closing connections tipc: hold a reference to nodes found by link name Revert "wifi: libertas: reject short monitor TX frames" selinux: fix data race on AVC latest_notif selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts sctp: copy zeroed stats to user in sctp_getsockopt_pr_streamstatus() when !streamoute EDAC/amd64: Mask UMC chip select to the four implemented selects gpio: mpsse: fix race when arming the IRQ poll worker gpio: xilinx: fix runtime PM leak on request error path gve: fix napi_disable deadlock when attempting to disable XSK pools gve: fix XSK buffer leak when rings are stopped gve: fix XSK buffer leak on error descriptor ibmveth: h_free logical LAN on open-fail after register ibmveth: fix TX LTB and filter unwind on open-fail ice: fix use-after-free in dynamic port cleanup ice: fix metadata_dst refcount handling on representor teardown keys: finalize persistent keyring timeout after link attempt KEYS: Fix add_key() race with keyring restriction memstick: core: wait for request completion before freeing card memstick: rtsx_usb_ms: complete requests after eject instead of dropping them mm: don't schedule deferred kernel page table freeing while booting dm-crypt: reject the lmk IV mode with AEAD ciphers dm-integrity: fix buffer overflow in inline mode with large tag size dm-snap: reject the transient exception store for snapshot-merge dm: fix reading free memory in do_resume mmc: cavium-octeon: destroy slot platform devices on remove mmc: cavium-thunderx: destroy slot platform devices on remove mmc: mtk-sd: Cancel request timeout work on remove mmc: sdhci-sprd: disable runtime PM on remove net/packet: guard the ll header push in packet_rcv_spkt() net/smc: protect clcsock lifetime in smc_getname net: bridge: avoid recursive multicast port cleanup net: dsa: microchip: fix KSZ8765 fiber detection net: skbuff: don't leave stale bytes in skb_copy_and_csum_bits() net: sparx5: free the matchall entry on destroy net: usb: ax88179_178a: fix rx frame length for non-last packets net: team: stop reusing skb after queue override net: team: free skb when broadcast has no txable port nvme: fix swapped ZRASF zone state values for full and read only openvswitch: fix soft lockup in the netlink flow dump optee: register TEE devices only once fully initialized regulator: ltc3676: don't read the write-only HRST and CLIRQ registers regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4 pmdomain: imx8m-blk-ctrl: Serialize power on/off across sibling domains pmdomain: rockchip: don't ignore clock lookup errors on attach pmdomain: rockchip: fix clock leak on domain probe failure pmdomain: rockchip: propagate subdomain add errors scsi: qedi: Initialize callback state before registration riscv: entry: gate shadow call stack reload on sstatus.SPP, not tp riscv: errata: select RISCV_ALTERNATIVE_EARLY for THEAD GHOSTWRITE riscv: fix load_unaligned_zeropad() fixup for RV32 riscv: futex: untag the user pointer before the atomic access riscv: hwprobe: use _BITULL() rather than BIT() in MIPS vendor uapi header Bluetooth: btintel_pcie: use managed IRQ teardown Bluetooth: hci_sock: Serialize dead-device detachment Bluetooth: hci_sync: Fix command skb lifetime during scan setup Bluetooth: ISO: Reject concurrent BIS listener setup Bluetooth: ISO: Serialize concurrent connect calls Bluetooth: MGMT: Fix status of pending commands flushed on power off Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() Bluetooth: RFCOMM: free the skb when the DLC has no owner Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN drm/gud: don't keep a connector without a CRTC as connector_state drm/i915/gem: Prevent overstepping exec array boundary drm/i915/gt: Unmask interrupts only when ACTIVE is true drm/imagination: Size page table preallocation by device address drm/vc4: drain the hangcheck timer and works on V3D unbind drm/vc4: Fix firmware reference leak in vc4_drm_bind() drm/vmwgfx: validate pitch coming from userspace drm/xe: Fix shrinker accounting double-subtraction on nested external pins drm/xe: Fix stale pinned_link entry when fb-pin performs the final unpin drm/amdkfd: align SDMA doorbell base for shader doorbell writes drm/amdkfd: fix dma_buf reference leak in get_dmabuf_info drm/amdgpu: serialize vblank counter reads against GPU reset drm/amdgpu: make Mac FB workaround generic drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks drm/amdgpu/userq: only accept doorbell BOs as queue doorbell drm/amdgpu/userq: return the memdup_user() error for the user MQD drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs mount: keep a copied mount unbindable fs: don't silently unmount busy mounts namespace: reset the old parent's ->overmount in mnt_change_mountpoint() namespace: don't inherit MNT_UMOUNT in clone_mnt() namespace: don't copy an unmounted mount tree fs: refuse fspick() on internal superblocks namespace: check the target before walking it in do_mount_setattr() namespace: queue a mount only once for mount notifications namespace: check a submount for references right before unmounting it namespace: check a recursive bind mount for mount namespace loops namespace: look at the topmost mount for a mount namespace file namespace: remove the fsnotify marks of a mount namespace in process context namespace: check the mounts before reading their parents in pivot_root() dcache: don't put a mountpoint on a dentry that's being removed namespace: don't let a pseudo dentry become the root of a mount namespace: unhash a dentry before detaching the mounts on it namei: don't reveal overmounted entries in refwalk fcntl: refuse F_SET_RW_HINT on an immutable inode namespace: refuse an automount below a mount that is in no namespace namespace: never expire a locked mount namespace: handle mount locking for automounts correctly ata: libata-scsi: do not lose CHECK CONDITION for failed ATAPI commands accel/amdxdna: Fix NULL pointer dereference of mgmt_chann drm/xe/vf: Add drm_dev guards when detaching CCS read/write buffers accel/amdxdna: Refactor GEM BO handling and add helper APIs for address retrieval tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy() RDMA/bnxt_re: Add a max slot check for SQ netfilter: nft_fwd_netdev: add device and headroom validate with neigh forwarding s390/zcrypt: Move inline function rng_type6cprb_msgx from header to code s390/zcrypt: Close speculative mem read possibility octeontx2-af: Block VFs from clobbering special CGX PKIND state KVM: arm64: vgic: Fix race between LPI release and re-registration drm/amdkfd: Fix infinite loop parsing CRAT with zero subtype length NTB: core: Add .get_dma_dev() callback to ntb_dev_ops NTB: ntb_transport: Use ntb_get_dma_dev() for DMA buffers svcrdma: Add Write chunk WRs to the RPC's Send WR chain svcrdma: wake sq waiters when the transport closes kho: fix size calculation in kho_preserved_memory_reserve() lockd, nfsd: RCU-protect nlmsvc_ops dispatch LoongArch: KVM: Validate MSI data before routing it to EIOINTC dpll: fix NULL deref in dpll_device_ops() during teardown race ksmbd: detach blocked lock requests before freeing ksmbd: defer publishing granted locks to prevent UAF/double-free race ksmbd: serialize oplock close with pending break ownership blk-cgroup: delay freeing policy data after rcu grace period PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers bpf: Invalidate RCU pointers after final spin unlock drm/amd/display: Fix dangling pointer in CRTC reset function bpf: Keep refcount_acquire nullable for borrowed RCU kptrs ring-buffer: Skip invalid sub-buffers when validating persistent ring buffer ipv6: mcast: annotate data-races around mca_users arm64: dts: lx2160a: fix incorrect pinmux arm64: dts: lx2160a: fix IIC1 pinmux submask rejected by pinctrl-single arm64: dts: lx2160a: fix the iic5 spi3 pinmux offset and value mount: refuse MOVE_MOUNT_SET_GROUP on an unbindable mount fs: don't let a migrating task hide its reference from do_umount() Bluetooth: btintel_pcie: fix TX descriptor bounds check Bluetooth: btintel_pcie: Add shared HW reset for clean start drm/dp: don't mark the AUX backlight enabled when enabling failed gpio: exar: initialize the ID before registering its cleanup drm/aspeed: Balance the display clock enable on teardown drm/vc4: Free the BO cache size list on teardown net/sched: em_text: reject unterminated algo before autoload amt: send the relay's General Query directly from the receive path cxgb4/ch_ktls: disable softirqs around tid_list erases tee: optee: fix kernel-doc warnings tee: optee: ffa: support shared memory offsets on large-page kernels ice: Restore Ordered MMIO Writes for Tx Doorbells nvmet: return Invalid Field for invalid NSIDs feature 82h nvmet: use the local P2P device on metadata allocation failure arm64/boot: Don't set PMUv3p9 FGT2 bits without PMUv3 zloop: zero out only the unread tail of short reads btrfs: always return -EIOCBQUEUED after btrfs_uring_read_extent_endio btrfs: free iov when btrfs_uring_read_extent() fails btrfs: unlock inode and extent in caller when io_uring read extent fails btrfs: fix xattr replace when multiple xattrs are packed in the same item btrfs: fix lost error return value in btrfs_listxattr() drm/xe/mmio: Fix xe_mmio_wait32() to honor delay/sleep maximums net: make dev_xdp_sb_prog_count() see programs attached through a link riscv: vector: Fix data pointer constraints in context save/restore riscv: vector: Fix output operands in context save wifi: mt76: don't return TXQ when exceeding max non-AQL packets wifi: mac80211: add AQL support for multicast packets wifi: mac80211: add ieee80211_txq_aql_pending() wifi: mt76: add PS buffering support for HW-managed TIM drivers wifi: mt76: account non-AQL frames per peer rather than per link wifi: mt76: route nullfunc frames to PSD/ALTX queue wifi: mt76: use ALTX queue for packets to disassociated stations wifi: mt76: mt7925: restore the legacy BSS after MLO teardown wifi: mt76: mt7996: fix struct mt7996_mcu_wed_rro_ba_delete_event layout wifi: mt76: mt7915: disable rx napi when removing device wifi: mt76: mt7925: don't put the band auto marker in TGID wifi: mt76: mt792x: treat 0xff ACPI SAR entries as no limit wifi: mt76: mt792x: pick the SAR table layout from the table itself Revert "wifi: ath12k: add panic handler" ASoC: adau1372: allow sleepy powerdown GPIOs ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM spi: sg2044-nor: Return transfer errors spi: sg2044-nor: Honor SPI clock limits cgroup/cpuset: Call is_in_v2_mode() after acquiring cpuset_mutex in cpuset_handle_hotplug() flow_dissector: avoid u16 truncation of skb->len when computing thoff net: sparx5: start the TOD counters on non-PTP lan969x variants devlink: fix devlink_rel reference leak when notify work is pending net/sched: cls_route: reject change with no routing attribute Revert "net/mlx5: E-Switch, preserve max tx speed on vport state modification" net: bcmgenet: if UMAC was suspended in SW_RESET, restore it to SW_RESET pfcp: make sure the SEID is linear before reading it bnxt_en: Add bnxt_clear_bars() helper bnxt_en: Fix driver init in kdump kernel bnxt_en: Delay for 5 seconds after AER DPC for all chips bnxt_en: Drop pci_save_state() after pci_restore_state() bnxt_en: Re-write the BARs following any type of PCIe errors flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect() drm/imagination: Fix reference and vm_bo handling in remap() veth: fix peer NETDEV_XDP_ACT_NDO_XMIT after GRO is toggled while down net/mlx5e: Order ICOSQ cc update after CQ doorbell mlxsw: spectrum_flower: Fix port range register leak in tmplt_create() ptp: ocp: fix PCIe delay estimation calculation net: openvswitch: validate transport header presence in set_ipv6_addr vsock: Fix memory leak in vmci_transport_recv_dgram_cb() drm/vc4: Fix binner slot allocation failing on an idle GPU x86/CPU/AMD: Fix AMD TLBI Erratum #1718 drm/panthor: validate userspace queue count against initialized firmware slot count s390/zcrypt: Improve CCA CPRB length and overflow checks s390/zcrypt: Improve EP11 CPRB length and overflow checks s390/zcrypt: Improve EP11 CPRB domain handling with ASN.1 parsing s390/zcrypt: Pad trailing CCA or EP11 message with zeros xfs: remove duplicate INO1_WRITTEN check xfs: stop exchanging reflink flags when exchanging mappings xfs: fix exchange-range-to-eof file size exchange can: fix unique skb identifier regression under RPS SUNRPC: Add Kconfig dependency on CRYPTO_KRB5 regulator: of: fill in supply names in of_regulator_bulk_get_all() drm/amd/display: Don't replace a sink mode that shares the native totals sched_ext: Generate qseq from a per-task counter HID: steam: Fully unregister controller when hidraw is opened HID: steam: Rearrange teardown sequence HID: steam: Refactor registration HID: steam: Clean up locking ipv4: udp: Create exceptions before socket matching ipv6: udp: Create exceptions before socket matching can: dev: init_can_skb(): restore skb header initialization e1000e: add system to disable K1 list fsverity: RCU-delay the freeing of struct fsverity_info iavf: iavf_virtchnl_completion: drop duplicate ether_addr_equal() test iavf: send MAC change request synchronously io_uring/register: don't exempt disabled rings from task restrictions ip6_tunnel: do not use dst6_mtu() in ip4ip6_err() and ip6erspan_tunnel_xmit() ip6_gre: remove obsolete ERSPAN PMTU update mm/vma: introduce vma_test[_any[_mask]](), and make inlining consistent mm/mremap: fix locked_vm leak by splitting VMA for MREMAP_DONTUNMAP net: xilinx: axienet: Free outstanding DMA buffers on dmaengine stop power: sequencing: pcie-m2: Fix leaking array from of_regulator_bulk_get_all() scsi: ch: Do not keep references to data transfer element devices scsi: ufs: core: Avoid unsafe MMIO reads in ufshcd_mcq_compl_all_cqes_lock() scsi: ufs: core: Decouple CQ sweep from request iterator in MCQ riscv: patch: fix handling of bpf-jit execmem addresses riscv: ptrace: reject CFI regset access when extensions are absent Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex drm/xe/i2c: cancel the client work on remove drm/amd/display: disable self-refresh on tearing flips statmount: read the parent of an unmounted mount under mount_lock namespace: keep covered mounts covered in OPEN_TREE_NAMESPACE namespace: don't reconfigure internal superblocks via remount and umount unshare: don't drop active namespace references that were never taken nullfs: don't update the access time clk: qcom: gcc-kaanapali: Fix always-enabling PCIE_RSCC clocks clk: qcom: gpucc-kaanapali: Mark the GPU CX GDSC as votable iommu/dma: skip swiotlb bounce for DMA_ATTR_MMIO in iommu_dma_map_phys scsi: ufs: core: Hold a clock reference across the probe drm/bridge: Fix unlocked list_del in drm_bridge_add() drm/bridge: Fix unlocked list access in drm_bridge_attach() cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode() drm/vc4: Use kvmalloc_objs() for the BO cache size list lib/dim: fix 32-bit overflow in dim_calc_stats() rates net: stmmac: propagate PTP addend and system time programming errors bonding: fix the program leak when XDP is replaced btrfs: don't stash io_uring encoded data across -EAGAIN drm/xe: Do not emit Wa_16010904313 twice net/mlx5: Lag, split aggregate speed into oper and max helpers net: stmmac: Do not advertise S-VLAN stripping when it is disabled net: stmmac: Disable S-Tag processing on dwmac4 net: airoha: Add retry mechanism to airoha_qdma_set_trtcm_param() Revert "net: stmmac: propagate PTP addend and system time programming errors" scsi: ufs: mediatek: Handle mPHY power-on failures net: always dissect GSO packets in __virtio_net_hdr_to_skb() ASoC: sdw_utils: Add codec info for CS35L62 ASoC: sdw_utils: Switch CS35L56/57/62/63 to use OT25 DAI riscv: ptrace: Zero-initialize regset buffers before copyin bareudp: set the inner protocol to the protocol of the packet net/packet: call packet_parse_headers after virtio_net_hdr_to_skb drm/vc4: Use devm_request_irq() for automatic cleanup drm/vc4: Disable the V3D interrupt across runtime suspend io_uring/memmap: account the pages a compound region really uses io_uring/zcrx: use better name for RQ region io_uring: cast id to u64 before shifting in io_allocate_rbuf_ring() io_uring/zcrx: use correct mmap off constants io_uring: do not charge the SQ/CQ rings to RLIMIT_MEMLOCK io_uring/kbuf: don't charge provided buffer rings to RLIMIT_MEMLOCK mm/mremap: fix locked_vm leak from MREMAP_DONTUNMAP self-merge UBUNTU: Upstream stable to v6.18.57, v7.2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171601/+subscriptions

[Bug 2171810] Re: Mainline Kernel Builds Stopped

** 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/2171810 Title: Mainline Kernel Builds Stopped Status in linux package in Ubuntu: New Bug description: kernel.ubuntu.com/mainline has not published new builds since mid- September 2026. Evidence (checked 2026-10-21): - Latest daily: 2026-09-17 (7.3.0-070300rc3daily20260917). No daily dirs after that date. - Latest tagged dir: v7.3-rc3 (2026-09-14). v7.3-rc4, rc5, rc6, rc7 and v7.3 (final, tagged upstream 2026-10-18) do not exist. - https://kernel.ubuntu.com/mainline/v7.3/ returns 404. - The last daily run itself built fine on amd64, arm64, armhf, ppc64el and s390x. amd64 self-tests failed (rc=2). i386 build failed after 8s (rc=2). riscv64 reported success in 10s with no .debs. This looks like the scheduler/trigger stopped, not a compile failure. Similar multi-week stalls happened in Oct 2023 and Sep 2024. Request: please restore the build pipeline, and publish v7.3-rc4 through v7.3 if possible. Commands used: curl -s https://kernel.ubuntu.com/mainline/ | grep -E 'v7\.3' curl -s https://kernel.ubuntu.com/mainline/daily/ | grep -oE 'href="[0-9-]+/"' | tail -5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171810/+subscriptions

[Bug 2171818] Re: amdgpu reports incomplete modes list for screen attached via USB-C

** 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/2171818 Title: amdgpu reports incomplete modes list for screen attached via USB-C Status in linux package in Ubuntu: New Bug description: I have a laptop (with two AMD GPUs) that I often connect to a 4k DELL monitor using an USB-C cable. Sometimes amdgpu seems to set an incomplete list of supported modes for this monitor when I first connect it, so Gnome cannot use its stored configuration for it. This is clearly seen in the logs: gnome-shell[5629]: Failed to use stored monitor configuration: Invalid mode 3840x2160 (120,000) for monitor 'DEL DELL S2725QC' This might be a race condition, because the problem doesn't always happen. The logs in this report show the problem happening as the laptop wakes up from sleep (at 00:05) with the monitor connected. (But waking up from sleep is not required, I often see this problem when I connect the monitor to an already awake laptop.) Then at 00:12 I disconnected and reconnected the monitor, and this second time it got all of its modes properly enumerated. I never managed to reproduce the problem by repeatedly disconnecting and reconnecting the monitor, I've only ever experienced it on the first time it gets connected (per reboot). I've attached to this report: - /sys/class/drm/card*-*/status and modes for both the incorrect and correct states - system and user journalct output - ~/.config/monitors.xml - version info on relevant components 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/controlC2: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC1: dszoboszlay 5088 F.... wireplumber /dev/snd/controlC0: dszoboszlay 5088 F.... wireplumber /dev/snd/seq: dszoboszlay 5082 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 00:19:57 2026 InstallationDate: Installed on 2024-12-25 (665 days ago) InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA402RK_GA402RK ProcFB: 0 amdgpudrmfb 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-05-24 (151 days ago) dmi.bios.date: 07/01/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GA402RK.313 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA402RK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: gametopia dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGA402RK.313:bd07/01/2022:br5.24:efr3.12:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA402RK_GA402RK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA402RK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGZephyrusG14: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA402RK_GA402RK 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/2171818/+subscriptions