[Bug 2163610] [NEW] OVTI08F4 camera fails to probe on HP Spectre x360 14-eu0xxx (error -121)

Public bug reported: I am reporting a built-in camera failure on an HP Spectre x360 2-in-1 Laptop 14-eu0xxx. System - Ubuntu 26.04 LTS - linux-image-7.0.0-29-generic, package version 7.0.0-29.29 - Camera sensor: OVTI08F4 / OmniVision ov08x40 - Intel IPU6 camera stack Expected result The ov08x40 sensor should probe and the built-in camera should be available to libcamera and desktop camera applications. Actual result The sensor fails to read its chip ID and the camera is unavailable: ov08x40: error reading chip-id register: -121 What I found The existing 45 ms INT3472 handshake delay is not long enough on this laptop. A 150 ms delay allows the sensor to probe. I prepared a DMI-scoped quirk so the longer delay is used only for the matching HP Spectre x360 14-eu0xxx family. After the sensor probes, libcamera also needs the ov08x40 driver to report the native size, crop bounds, and active crop through get_selection(). Without that, camera setup fails with rectangle ioctl errors. Testing I applied both kernel patches to the Ubuntu 7.0.12 source from linux-source-7.0.0 package version 7.0.0-29.29 and built the three affected modules for 7.0.0-29-generic. The patches passed scripts/checkpatch.pl --strict. The rebuilt modules were signed for Secure Boot, installed, and loaded after reboot. With the patches applied: - the sensor was detected and the -121 probe error did not return; - libcamera detected one camera and captured 60 consecutive 3848x2416 frames at 30 fps; - PipeWire exposed the built-in front camera; and - GNOME Snapshot showed a stable live preview. Patches and full validation notes https://github.com/liondragon/hp-spectre-ov08x40-camera Kernel patches https://github.com/liondragon/hp-spectre-ov08x40-camera/tree/main/patches/linux Validation record https://github.com/liondragon/hp-spectre-ov08x40-camera/blob/main/docs/validation.md ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163610 Title: OVTI08F4 camera fails to probe on HP Spectre x360 14-eu0xxx (error -121) Status in linux package in Ubuntu: New Bug description: I am reporting a built-in camera failure on an HP Spectre x360 2-in-1 Laptop 14-eu0xxx. System - Ubuntu 26.04 LTS - linux-image-7.0.0-29-generic, package version 7.0.0-29.29 - Camera sensor: OVTI08F4 / OmniVision ov08x40 - Intel IPU6 camera stack Expected result The ov08x40 sensor should probe and the built-in camera should be available to libcamera and desktop camera applications. Actual result The sensor fails to read its chip ID and the camera is unavailable: ov08x40: error reading chip-id register: -121 What I found The existing 45 ms INT3472 handshake delay is not long enough on this laptop. A 150 ms delay allows the sensor to probe. I prepared a DMI-scoped quirk so the longer delay is used only for the matching HP Spectre x360 14-eu0xxx family. After the sensor probes, libcamera also needs the ov08x40 driver to report the native size, crop bounds, and active crop through get_selection(). Without that, camera setup fails with rectangle ioctl errors. Testing I applied both kernel patches to the Ubuntu 7.0.12 source from linux-source-7.0.0 package version 7.0.0-29.29 and built the three affected modules for 7.0.0-29-generic. The patches passed scripts/checkpatch.pl --strict. The rebuilt modules were signed for Secure Boot, installed, and loaded after reboot. With the patches applied: - the sensor was detected and the -121 probe error did not return; - libcamera detected one camera and captured 60 consecutive 3848x2416 frames at 30 fps; - PipeWire exposed the built-in front camera; and - GNOME Snapshot showed a stable live preview. Patches and full validation notes https://github.com/liondragon/hp-spectre-ov08x40-camera Kernel patches https://github.com/liondragon/hp-spectre-ov08x40-camera/tree/main/patches/linux Validation record https://github.com/liondragon/hp-spectre-ov08x40-camera/blob/main/docs/validation.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163610/+subscriptions

[Bug 2163601] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2163601/+attachment/5992614/+files/CRDA.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163601 Title: Regression: i915 backlight control broken on Dell XPS 13 Plus (9320, UHD+ panel) with kernel 7.0.0, worked on 6.17.0 Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 26.04 (kernel 7.0.0-generic), screen brightness can no longer be changed on a Dell XPS 13 Plus (9320) developer edition with the UHD+ 3840x2400 LCD panel (Alder Lake-P / Raptor Lake-P graphics, device ID a7a0, i915 driver). The GNOME brightness OSD appears and the slider moves, and the sysfs interface accepts values, but the panel brightness does not actually change. This is a regression: booting the previously installed 6.17.0-35-generic kernel on the same system, brightness control works normally. Kernels 7.0.0-28-generic and 7.0.0-29-generic are both affected. ## Symptoms / evidence - /sys/class/backlight contains only intel_backlight (no acpi_video0). - Writes to /sys/class/backlight/intel_backlight/brightness are accepted; both `brightness` and `actual_brightness` track the written value (max_brightness = 1023), but the panel does not change. - brightnessctl and the GNOME slider show the same behavior: values change, panel does not. - dmesg contains no backlight/PWM/panel errors at all. The only i915 anomaly is: `i915 0000:00:02.0: [drm] Selective fetch area calculation failed in pipe A` - Brightness set in the firmware setup (BIOS) works and persists into the 7.0.0 session, so the backlight hardware itself is functional; the OS just cannot drive it. - Brightness set while booted into 6.17.0-35 also persists into a subsequent 7.0.0 boot. ## Ruled out - i915.enable_psr=0: verified active via /sys/kernel/debug/dri/1/eDP-1/i915_psr_status (PSR mode: disabled). No effect on the bug. (With defaults, PSR2 is enabled and the panel sits in DEEP_SLEEP.) - i915.enable_dpcd_backlight=3: verified active via /sys/module/i915/parameters/enable_dpcd_backlight. No effect; max_brightness stayed at 1023, so the driver remained on the PWM path. This suggests the panel is PWM-dimmed and the regression is in the PWM backlight path. - Firmware is current (fwupd reports no pending updates). - Kernel driver in use is i915 (not xe). ## Regression window - Works: 6.17.0-35-generic (Ubuntu 25.10 kernel) - Broken: 7.0.0-28-generic, 7.0.0-29-generic (Ubuntu 26.04) ## Hardware - Dell XPS 13 Plus 9320, UHD+ 3840x2400 LCD (eDP-1), touch - Intel Alder Lake-P/Raptor Lake-P integrated graphics, device ID a7a0, display version 13.00 stepping E0 - Wayland session (GNOME), Secure Boot enabled (kernel lockdown: integrity) ## Workaround Boot 6.17.0-35 (or enter BIOS setup) to set a brightness level, which then persists into 7.0.0 sessions; brightness is otherwise fixed at that level. --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: saalfeld 5142 F.... pipewire saalfeld 5160 F.... wireplumber /dev/snd/seq: saalfeld 5142 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33 DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2023-08-25 (1087 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 MachineType: Dell Inc. XPS 9320 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=e3cab906-301b-4c1d-b143-48e1391c0a45 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: resolute wayland-session Uname: Linux 7.0.0-29-generic x86_64 UpgradeStatus: Upgraded to resolute on 2026-06-10 (67 days ago) UserGroups: adm cdrom dip docker lpadmin nordvpn ollama plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/28/2026 dmi.bios.release: 2.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.31.0 dmi.board.name: 0CR6NC 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.31.0:bd05/28/2026:br2.31:efr1.17:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn0CR6NC: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/2163601/+subscriptions

[Bug 2150605] Re: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm`

Same failure signature on Meteor Lake-P (the existing reports are mostly Arrow Lake). Adding a clean A/B between two Ubuntu HWE kernels on identical hardware and cmdline. Hardware - Lenovo ThinkPad P1 Gen 7, machine type 21KV001RMX - BIOS N48ET34W (1.21), 2026-05-11 - iGPU: 00:02.0 Intel Meteor Lake-P [Intel Arc Graphics] [8086:7d55] rev 08, driver i915 - dGPU: 01:00.0 NVIDIA AD107GLM [RTX 1000 Ada Generation Laptop GPU] [10de:28b9], nvidia 580.173.02 (DKMS) - Panel: eDP-1, 2560x1600, port_clock 810000 (HBR3, lane_count: 4, use_c10: yes) - Firmware: DMC i915/mtl_dmc.bin v2.21, GuC 70.36.0 (kernel recommends 70.53.0), HuC 8.5.4 - ACPI advertises S0 S4 S5 — s2idle only, no S3 - Ubuntu 24.04.4 LTS, X11 session (GNOME), iGPU runtime PM at default control=auto Kernels kernel package result 7.0.0-28-generic (base 7.0.12) 7.0.0-28.28~24.04.1 BAD — 41–54 s black screen on every resume 6.17.0-40-generic 6.17.0-40.40~24.04.1 GOOD — resume ~2.5 s, zero i915 errors Same cmdline, same dock, same session type. Only the kernel changed. Symptom Every resume from s2idle: backlight on, screen black, machine unusable for ~40–55 s, then the desktop appears normally. No hard failure — purely a stall. Failure sequence (7.0.0-28) Root cause is visible at the very top: the C10 PHY message bus is dead, so the PLL is never programmed, and every subsequent atomic commit waits out its full 10 s timeout. i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate (expected 282699, found 21444) i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 0000:00:02.0: [drm] *ERROR* expected: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no, use_c10: yes, tbt_mode: no i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes, i915 0000:00:02.0: [drm] *ERROR* found: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, i915 0000:00:02.0: [drm] *ERROR* c10pll_rawhw_state: i915 0000:00:02.0: [drm] *ERROR* tx: 0x0, cmn: 0x0 i915 0000:00:02.0: [drm] *ERROR* pll[0] = 0x0, pll[1] = 0x0, pll[2] = 0x0, pll[3] = 0x0 ... all 20 pll[] registers read back 0x0 ... i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in port_clock (expected 810000, found 61440) i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in min_voltage_level (expected 1, found 0) ------------[ cut here ]------------ i915 0000:00:02.0: [drm] pipe state doesn't match! WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state+0x51b/0x6c0 [i915], CPU#17: Xorg/6093 Same 61440 vs 810000 parked-PLL value as the Arrow Lake reports in this bug. Then four consecutive 10 s timeouts, which is where the wall-clock goes: 09:04:08 [CRTC:150:pipe A] flip_done timed out 09:04:18 flip_done timed out / [CRTC:150:pipe A] commit wait timed out 09:04:29 [CRTC:150:pipe A] flip_done timed out 09:04:29 [CRTC:150:pipe A] DSB 1 timed out waiting for idle (current head=0x12fc000, head=0x0, tail=0x1080) 09:04:39 flip_done timed out / [CRTC:150:pipe A] commit wait timed out 09:04:49 flip_done timed out / [CONNECTOR:507:eDP-1] commit wait timed out 09:04:50 [drm] PHY A failed to change powerdown state Caller is the compositor's DPMS-on after resume: Call Trace: intel_modeset_verify_crtc+0x70/0xb0 [i915] intel_atomic_commit_tail+0x8bb/0xc80 [i915] intel_atomic_commit+0x2c0/0x310 [i915] drm_atomic_commit+0xaf/0xf0 drm_atomic_connector_commit_dpms+0xfc/0x110 drm_mode_obj_set_property_ioctl+0x1c3/0x450 drm_connector_property_set_ioctl+0x3a/0x60 drm_ioctl_kernel+0xb7/0x110 An earlier boot on the same kernel produced the identical chain from intel_dbuf_mbus_post_ddb_update → intel_crtc_wait_for_next_vblank → drm_crtc_wait_one_vblank (vblank wait timed out on crtc 0), so the entry point varies but the parked-PLL cause is the same. Good kernel (6.17.0-40), same machine, same cmdline PM: suspend entry (s2idle) Restarting tasks: Starting Restarting tasks: Done PM: suspend exit - suspend entry → suspend exit = 19 s wall, of which /sys/power/suspend_stats/last_hw_sleep = 16 551 862 µs actually asleep ⇒ kernel-side resume ≈ 2.5 s - Zero i915 errors in the whole boot. No PHY A, no DDI BUF, no flip_done. - Reproduced twice, once with the nvidia modules absent and once with them loaded — identical. Ruled out on this machine - i915.enable_psr=0 i915.enable_panel_replay=0 — verified applied via /proc/cmdline, no effect, identical trace. (Consistent with other reports here.) - nvidia: 6.17 resumes fast both with nvidia 580.173.02 unloaded and loaded. No nvidia frame appears anywhere in the failing stack. - PM core / s2idle itself: /sys/power/suspend_stats shows success incrementing and all failed_* counters at 0; firmware sleep counters populate normally. The stall is entirely in the display commit path after PM: suspend exit. Notes - Does not require a multi-hour dwell here: two failures on the same boot were 29 minutes apart, so the dwell between them was under half an hour. Every resume on 7.0.0-28 failed. - Ubuntu currently offers nothing newer on this line: apt policy linux-image-generic-hwe-24.04 gives candidate = installed = 7.0.0-28.28~24.04.1, so 24.04 HWE users have no upgrade path out of this. Working around it by pinning 6.17.0-40-generic. Attaching the full scrubbed kernel log for both the bad 7.0.0-28 boot and the good 6.17.0-40 boot. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150605 Title: `i915 Arrow Lake-S: PHY A / C10 DPLL state mismatch on resume from long s2idle dwell — slow wake (5-10s) with retry storm` Status in linux package in Ubuntu: Confirmed Bug description: This is what an investigation using claude code yielded regarding a wake-up from sleep issue: On HP ZBook Fury G1i 16 (Arrow Lake-S, integrated display engine identifying as meteorlake D0, PCI 8086:7d67), every resume from s2idle after a multi-hour dwell produces a stack of i915 *ERROR* messages from the C10 PHY / DPLL state-restore path. The driver retries and eventually recovers, so the display *does* come back, but the retry loop takes ~5-10 seconds — long enough that users report "the display didn't wake up." Short cycles (seconds-to-minutes of dwell) wake instantly with no errors. The error stack is byte-for-byte identical across two reproductions and across `i915.enable_psr=0`, `i915.enable_dc=0`, and `i915.enable_fbc=0`. Those flags do not reach the code path that's racing. Earlier, before `i915.enable_psr=0` was applied, the same regime caused hard hangs (`Atomic update failure on pipe A`) requiring power-cycle. PSR-disable converted the failure mode from "hang" to "slow recover" but did not eliminate it. `xe.force_probe=7d67` was also tested as a workaround. xe binds cleanly on this device but suffers a different bug: `Tile0: GT0: Engine reset engine_class=rcs guc_id=48 state=0x289` repeating across each suspend cycle (`drm_WARN_ON_ONCE(ret == -110)`), eventually wedging the display. Not viable as a workaround on this kernel. NVIDIA dGPU is fully exonerated: `nvidia-suspend.service` and `nvidia-resume.service` `Finished` cleanly across every cycle. ## System * Distro: Ubuntu 26.04 LTS (resolute) * Kernel: 7.0.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:09:53 UTC 2026 x86_64 * Package: linux-image-7.0.0-14-generic 7.0.0-14.14 * Firmware pkg: linux-firmware 20260319.git217ca6e4.1ubuntu * HW: HP ZBook Fury G1i 16 inch Mobile Workstation PC, BIOS X96 Ver. 01.01.19 (2025-11-22) (latest per fwupdmgr) * iGPU: Intel Corporation Arrow Lake-S [Intel Graphics] [8086:7d67] (rev 06), driver: i915 * dGPU: NVIDIA Corporation GB205GLM [RTX PRO 3000 Blackwell Generation Laptop GPU] [10de:2f38] (rev a1), driver: nvidia 580.142 (open kernel modules) * Loaded i915 firmware: mtl_dmc.bin (v2.23), mtl_guc_70.bin v70.53.0, mtl_huc_gsc.bin v8.5.4 * Sleep mode: s2idle only (`ACPI: PM: (supports S0 S4 S5)` — firmware does not expose S3) * Kernel cmdline (current):   `quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0` * Session: KDE Plasma on Wayland (sddm) ## Reproduction 1. Boot, log in, do normal work (browser, IDE, terminals). 2. Close laptop lid (or `systemctl suspend`) for ≥2 hours. 3. Open lid / press a key. Expected: panel relights within ~500 ms, no kernel ERRORs. Actual: panel relights after ~5-10 s, journal contains the error stack below. ## Journal trace (boot 2026-04-29 05:48, dwell 05:51:11 → 07:59:21 = 2 h 8 min) ``` PM: suspend entry (s2idle) PM: Some devices failed to suspend, or early wake event detected PM: suspend exit PM: suspend entry (s2idle) [2 h 8 min later] PM: suspend exit i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate                        (expected 1220171, found 92553) i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 0000:00:02.0: [drm] *ERROR* expected: i915 0000:00:02.0: [drm] *ERROR* cx0pll_hw_state: lane_count: 4, ssc_enabled: no,                                    use_c10: yes, tbt_mode: no i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 810000, fracen: yes, i915 0000:00:02.0: [drm] *ERROR* quot: 61440, rem: 0, den: 1, i915 0000:00:02.0: [drm] *ERROR* multiplier: 210, tx_clk_div: 0. i915 0000:00:02.0: [drm] *ERROR* found: i915 0000:00:02.0: [drm] *ERROR* c10pll_hw_state: clock: 61440, fracen: no, i915 0000:00:02.0: [drm] *ERROR* multiplier: 16, tx_clk_div: 0. ``` The expected vs found C10 PLL clock (810 MHz HBR3 vs 61 MHz fallback) is the key signal: the panel's eDP link comes back at the wrong rate, the driver retries and eventually re-locks at the correct rate. This is in `drivers/gpu/drm/i915/display/intel_cx0_phy.c` / DPLL state restore — below the layers reachable by `enable_psr` / `enable_dc` / `enable_fbc`. ## What I have already tried | change | wake outcome on long dwell | |---|---| | (default) | hard hang, `Atomic update failure on pipe A`, requires power-cycle | | `i915.enable_psr=0` (only) | clean wake on short cycles, untested at long dwell | | `i915.enable_psr=0 i915.enable_dc=0` | slow recover (~5-10 s) at 6 h 41 min dwell, full error stack | | `... i915.enable_fbc=0` (added) | same: slow recover, identical error stack at 2 h 8 min dwell | | `i915.force_probe=!7d67 xe.force_probe=7d67` | xe binds cleanly, but `GT0: Engine reset` storm during cycles, eventual wedge | linux-firmware is at the latest candidate for 26.04 (20260319.git217ca6e4.1ubuntu). linux-image-oem-26.04 does not exist yet. ## Why this matters This is a clean reproduction of a likely-upstream Arrow Lake-S regression in the cx0/c10pll DPLL state-restore path during s2idle resume. The error signature is highly diagnostic and consistent across runs. Fix has not landed in 7.0.0-14.14; would benefit from being picked into the 26.04 kernel from upstream once available. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Wed Apr 29 08:18:09 2026 InstallationDate: Installed on 2026-03-27 (33 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260325) MachineType: HP HP ZBook Fury G1i 16 inch Mobile Workstation PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=2b2b39cc-2151-49f5-9205-74e3f9f1f999 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 zswap.enabled=1 zswap.compressor=zstd zswap.zpool=zsmalloc zswap.max_pool_percent=20 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2025 dmi.bios.release: 1.19 dmi.bios.vendor: HP dmi.bios.version: X96 Ver. 01.01.19 dmi.board.name: 8DE2 dmi.board.vendor: HP dmi.board.version: KBC Version 55.35.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 85.53 dmi.modalias: dmi:bvnHP:bvrX96Ver.01.01.19:bd11/22/2025:br1.19:efr85.53:svnHP:pnHPZBookFuryG1i16inchMobileWorkstationPC:pvrSBKPFV3:rvnHP:rn8DE2:rvrKBCVersion55.35.00:cvnHP:ct10:cvr:skuB14E7AV:pfa103C_5336ANHPZBook: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Fury G1i 16 inch Mobile Workstation PC dmi.product.sku: B14E7AV dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150605/+subscriptions

[Bug 2163555] Re: [ASUS ROG Strix G18 G814JVR] BIOS 320/322 expose conflicting ACPI namespace: duplicate XHCI _UPC/_PLD and PEGP._S0W definitions

** 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/2163555 Title: [ASUS ROG Strix G18 G814JVR] BIOS 320/322 expose conflicting ACPI namespace: duplicate XHCI _UPC/_PLD and PEGP._S0W definitions Status in linux package in Ubuntu: New Bug description: System: - ASUS ROG Strix G18 G814JVR - Ubuntu 26.04 LTS - kernel 7.0.0-29-generic / Ubuntu 7.0.0-29.29-generic - running-kernel ACPICA: 20251212 - BIOS tested: - G814JVR.320, 2024-10-24 - G814JVR.322, 2025-10-01 The system produces a large set of ACPI BIOS errors on every boot. I have isolated multiple reproducible namespace conflicts in the firmware ACPI tables and reproduced them independently with upstream ACPICA iasl 20260408. The most visible boot errors include: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.I2C1.TPL1], AE_NOT_FOUND ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.I2C3.TPL1], AE_NOT_FOUND and duplicate objects for every XHCI RHUB port: \_SB.PC00.XHCI.RHUB.HS01._UPC \_SB.PC00.XHCI.RHUB.HS01._PLD ... HS01 through HS14 SS01 through SS10 all failing with AE_ALREADY_EXISTS. Additional firmware errors include unresolved LPCB.SEN2, missing WMI WQ00, and \_TZ.THRM being unresolved while evaluating \_SB.IETM._OSC. I upgraded the machine from BIOS 320 to the current BIOS 322. The same ACPI errors remain. I captured the full ACPI table sets before and after the BIOS upgrade and compared them. The SSDTs directly implicated in these failures are byte-for-byte identical between BIOS 320 and BIOS 322, including: - ssdt1.dat (DPTF / thermal-related table) - ssdt7.dat (_ASUS_ RplSBTbt) - ssdt10.dat (_ASUS_ TbtTypeC) - ssdt11.dat (_ASUS_ UsbCTabl) - ssdt12.dat (INTEL xh_rplsb) - DMAR BIOS 322 did change the DSDT and several other tables, so it was a real firmware-table update, but the implicated SSDTs were not updated. I then built upstream ACPICA 20260408 and reproduced the namespace conflicts outside the running kernel. XHCI collision isolation: DSDT + ssdt12.dat (INTEL xh_rplsb) fails immediately with: Firmware Error (ACPI): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._UPC], AE_ALREADY_EXISTS This is the same error emitted by the running Ubuntu kernel. For comparison: - DSDT + ssdt10 (TbtTypeC): succeeds - DSDT + ssdt11 (UsbCTabl): succeeds - ssdt10 + ssdt11: succeeds - ssdt10 + ssdt12: succeeds - ssdt11 + ssdt12: succeeds Therefore the XHCI collision is specifically between the DSDT and the INTEL xh_rplsb SSDT, not between the ASUS Type-C tables. There is a second independent namespace collision: ssdt5.dat (SaSsdt) ssdt7.dat (_ASUS_ RplSBTbt) Both combinations: target=ssdt5 external=ssdt7 target=ssdt7 external=ssdt5 fail with: Failure creating named object [\_SB.PC00.PEG1.PEGP._S0W], AE_ALREADY_EXISTS The complete BIOS-322 table set also fails ACPICA 20260408 disassembly on that same PEGP._S0W object. The extracted AML further shows that the DSDT and INTEL xh_rplsb table provide overlapping XHCI RHUB port _UPC/_PLD definitions rather than the tables being mutually exclusive. This demonstrates an internally conflicting ACPI namespace supplied by the G814JVR firmware and reproducible with both the ACPICA version in the Ubuntu kernel and upstream ACPICA 20260408. There is a separate runtime xHCI/USB failure being tracked in Ubuntu bug #2163551. That incident involved an xHCI Host System Error and an IOMMU/DMAR DMA-read fault for 00:14.0. Because these ACPI errors concern the same XHCI controller namespace, they may be relevant platform context, but I am NOT claiming that the ACPI namespace defect has been proven to cause the runtime xHCI failure. Please advise whether this should be handled with a kernel ACPI quirk/table override or escalated to ASUS/firmware vendor, and whether any additional ACPI table analysis is useful. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 22:06:34 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) dmi.bios.date: 10/01/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.322 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR 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.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.322:bd10/01/2025:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR 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/2163555/+subscriptions

[Bug 2163568] Re: [i915][xe] Failed to read TMDS config: -6 on HDMI-A-1 (Alder Lake-P iGPU, Acer Aspire A715-76G) - external monitor never lights up

** 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/2163568 Title: [i915][xe] Failed to read TMDS config: -6 on HDMI-A-1 (Alder Lake-P iGPU, Acer Aspire A715-76G) - external monitor never lights up Status in linux package in Ubuntu: New Bug description: Summary ------- External HDMI monitor connected to the Intel iGPU HDMI port never gets a picture. Kernel log repeats every ~16 seconds since boot: [drm] *ERROR* [CONNECTOR:516:HDMI-A-1] Failed to read TMDS config: -6 `xrandr` shows HDMI-1 as "connected" but with an implausible fallback resolution (6880x2880), consistent with a failed EDID/DDC read rather than a real mode. Hardware -------- - Laptop: Acer Aspire A715-76G - iGPU: Intel Alder Lake-P UHD Graphics [8086:46a3] (0000:00:02.0) - HDMI port is wired to this GPU - dGPU: NVIDIA RTX 2050 (GA107), mux-less Optimus, no physical video output of its own - BIOS: InsydeH20, version V1.57 (2026-05-28) - latest available, no relevant multi-monitor/IGD options exposed - OS: Ubuntu 26.04 - Kernel: 7.0.0-29-generic (also reproduced on mainline-adjacent `xe` force-probe of the same kernel) Steps to reproduce ------------------ 1. Cold boot into Ubuntu with an external monitor connected via HDMI. 2. Monitor is detected but shows no signal / no picture. 3. `journalctl -k -b | grep -i -E "tmds|hdmi"` shows repeated "Failed to read TMDS config: -6" (errno -6 = ENXIO) on CONNECTOR:516:HDMI-A-1. What I already ruled out ------------------------- - Cable: tested with a second HDMI cable, same result. - Port/monitor: monitor+cable tested and recognized fine; same monitor works perfectly under Windows 11 on the exact same hardware/cable/port (both cold boot and warm reboot from a fully logged-in Windows session into Ubuntu). - prime-select mode: tested both `nvidia` and `on-demand`, no difference (expected, since the HDMI port is physically on the iGPU, not the dGPU). - Driver: forced the newer `xe` driver via `i915.force_probe=!46a3 xe.force_probe=46a3` - identical "Failed to read TMDS config: -6" error occurs with `xe` as well, just with the `xe` module name in the log instead of `i915`. This points to a failure in the shared GMBUS/DDC/i2c transaction layer, not in driver-specific logic. - BIOS: no Internal Graphics / IGD Multi-Monitor / DVMT / CSM options exist in this InsydeH20 BIOS to test. - Newer kernel: attempted to test mainline v7.1.5, but it fails to boot due to Secure Boot ("bad shim lock signature") since mainline builds are unsigned; not tested with Secure Boot disabled. Expected behavior ----------------- External HDMI monitor should light up on Linux the same way it does on Windows with identical hardware. Additional info ---------------- Please find attached: `journalctl -k -b` output, `lspci -nnk` VGA section, `xrandr` output, and dmesg from apport. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: alex 3919 F.... pipewire alex 3933 F.... wireplumber /dev/snd/seq: alex 3919 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 14:45:00 2026 InstallationDate: Installed on 2026-08-14 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Acer Aspire A715-76G 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-29-generic root=UUID=34813e31-7b29-4b9f-8baa-6216c89d517a 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/28/2026 dmi.bios.release: 1.57 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Metis_ADP dmi.board.vendor: ADL dmi.board.version: V1.57 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.57:bd05/28/2026:br1.57:efr1.4:svnAcer:pnAspireA715-76G:pvrV1.57:rvnADL:rnMetis_ADP:rvrV1.57:cvnChassisManufacturer:ct10:cvrChassisVersion:sku0000000000000000:pfaAspire7: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-76G dmi.product.sku: 0000000000000000 dmi.product.version: V1.57 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163568/+subscriptions

[Bug 2163585] Re: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

** 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/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough:   mkdir -p ~/hellomod && cd ~/hellomod   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c   printf 'obj-m += hello.o\n' > Makefile   make -C /lib/modules/$(uname -r)/build M=$PWD modules   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg:   module: x86/modules: Invalid relocation target, existing value is   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has:   Offset Type Symbol   0x138 R_X86_64_64 init_module + 0   0x490 R_X86_64_64 cleanup_module + 0 Environment:   Ubuntu 26.04 LTS   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46   Modules built with the same gcc 15.2.0 — vermagic matches   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so     there is no version skew between the running kernel and the build     headers   Secure Boot enabled, MOK enrolled, signing verified working (an     unsigned module fails differently, with "Key was rejected by service")   CONFIG_MODULE_COMPRESS_ZSTD=y   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting     with indirect_target_selection=off makes no difference   nvidia on this system is the prebuilt linux-modules-nvidia-595-open     package, built alongside the kernel rather than via DKMS, so it is     not a working out-of-tree counter-example. There are no other DKMS     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. Regression in 7.0.0-29-generic: out-of-tree modules fail to load with "Invalid relocation target" on .gnu.linkonce.this_module (works on 7.0.0-27) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: matt 5277 F.... wireplumber  /dev/snd/controlC0: matt 5277 F.... wireplumber  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb:  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=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: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2163585] Re: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

** Description changed: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: - mkdir -p ~/hellomod && cd ~/hellomod - printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c - printf 'obj-m += hello.o\n' > Makefile - make -C /lib/modules/$(uname -r)/build M=$PWD modules - sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ - /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko - sudo insmod hello.ko +   mkdir -p ~/hellomod && cd ~/hellomod +   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c +   printf 'obj-m += hello.o\n' > Makefile +   make -C /lib/modules/$(uname -r)/build M=$PWD modules +   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ +     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko +   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: - module: x86/modules: Invalid relocation target, existing value is - nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val - ffffffffc34c0010 +   module: x86/modules: Invalid relocation target, existing value is +   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val +   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: - Offset Type Symbol - 0x138 R_X86_64_64 init_module + 0 - 0x490 R_X86_64_64 cleanup_module + 0 +   Offset Type Symbol +   0x138 R_X86_64_64 init_module + 0 +   0x490 R_X86_64_64 cleanup_module + 0 Environment: - Ubuntu 26.04 LTS - Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 - Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 - Modules built with the same gcc 15.2.0 — vermagic matches - linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so - there is no version skew between the running kernel and the build - headers - Secure Boot enabled, MOK enrolled, signing verified working (an - unsigned module fails differently, with "Key was rejected by service") - CONFIG_MODULE_COMPRESS_ZSTD=y - CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting - with indirect_target_selection=off makes no difference - nvidia on this system is the prebuilt linux-modules-nvidia-595-open - package, built alongside the kernel rather than via DKMS, so it is - not a working out-of-tree counter-example. There are no other DKMS - modules installed to compare against. +   Ubuntu 26.04 LTS +   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 +   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 +   Modules built with the same gcc 15.2.0 — vermagic matches +   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so +     there is no version skew between the running kernel and the build +     headers +   Secure Boot enabled, MOK enrolled, signing verified working (an +     unsigned module fails differently, with "Key was rejected by service") +   CONFIG_MODULE_COMPRESS_ZSTD=y +   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting +     with indirect_target_selection=off makes no difference +   nvidia on this system is the prebuilt linux-modules-nvidia-595-open +     package, built alongside the kernel rather than via DKMS, so it is +     not a working out-of-tree counter-example. There are no other DKMS +     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. + + Regression in 7.0.0-29-generic: out-of-tree modules fail to load with + "Invalid relocation target" on .gnu.linkonce.this_module (works on + 7.0.0-27) + ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC1: matt 5277 F.... wireplumber - /dev/snd/controlC0: matt 5277 F.... wireplumber - /dev/snd/seq: matt 5271 F.... pipewire +  USER PID ACCESS COMMAND +  /dev/snd/controlC1: matt 5277 F.... wireplumber +  /dev/snd/controlC0: matt 5277 F.... wireplumber +  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse - Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro - Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub +  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub +  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse +  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro +  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth +  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> +  LANG=en_US.UTF-8 +  PATH=(custom, no user) +  SHELL=/bin/bash +  TERM=xterm-256color +  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=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: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough:   mkdir -p ~/hellomod && cd ~/hellomod   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c   printf 'obj-m += hello.o\n' > Makefile   make -C /lib/modules/$(uname -r)/build M=$PWD modules   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg:   module: x86/modules: Invalid relocation target, existing value is   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has:   Offset Type Symbol   0x138 R_X86_64_64 init_module + 0   0x490 R_X86_64_64 cleanup_module + 0 Environment:   Ubuntu 26.04 LTS   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46   Modules built with the same gcc 15.2.0 — vermagic matches   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so     there is no version skew between the running kernel and the build     headers   Secure Boot enabled, MOK enrolled, signing verified working (an     unsigned module fails differently, with "Key was rejected by service")   CONFIG_MODULE_COMPRESS_ZSTD=y   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting     with indirect_target_selection=off makes no difference   nvidia on this system is the prebuilt linux-modules-nvidia-595-open     package, built alongside the kernel rather than via DKMS, so it is     not a working out-of-tree counter-example. There are no other DKMS     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. Regression in 7.0.0-29-generic: out-of-tree modules fail to load with "Invalid relocation target" on .gnu.linkonce.this_module (works on 7.0.0-27) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: matt 5277 F.... wireplumber  /dev/snd/controlC0: matt 5277 F.... wireplumber  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb:  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=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: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2163585] [NEW] No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

Public bug reported: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: mkdir -p ~/hellomod && cd ~/hellomod printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c printf 'obj-m += hello.o\n' > Makefile make -C /lib/modules/$(uname -r)/build M=$PWD modules sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: module: x86/modules: Invalid relocation target, existing value is nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: Offset Type Symbol 0x138 R_X86_64_64 init_module + 0 0x490 R_X86_64_64 cleanup_module + 0 Environment: Ubuntu 26.04 LTS Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 Modules built with the same gcc 15.2.0 — vermagic matches linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so there is no version skew between the running kernel and the build headers Secure Boot enabled, MOK enrolled, signing verified working (an unsigned module fails differently, with "Key was rejected by service") CONFIG_MODULE_COMPRESS_ZSTD=y CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting with indirect_target_selection=off makes no difference nvidia on this system is the prebuilt linux-modules-nvidia-595-open package, built alongside the kernel rather than via DKMS, so it is not a working out-of-tree counter-example. There are no other DKMS modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: matt 5277 F.... wireplumber /dev/snd/controlC0: matt 5277 F.... wireplumber /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=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: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS ** 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/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: mkdir -p ~/hellomod && cd ~/hellomod printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c printf 'obj-m += hello.o\n' > Makefile make -C /lib/modules/$(uname -r)/build M=$PWD modules sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: module: x86/modules: Invalid relocation target, existing value is nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: Offset Type Symbol 0x138 R_X86_64_64 init_module + 0 0x490 R_X86_64_64 cleanup_module + 0 Environment: Ubuntu 26.04 LTS Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 Modules built with the same gcc 15.2.0 — vermagic matches linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so there is no version skew between the running kernel and the build headers Secure Boot enabled, MOK enrolled, signing verified working (an unsigned module fails differently, with "Key was rejected by service") CONFIG_MODULE_COMPRESS_ZSTD=y CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting with indirect_target_selection=off makes no difference nvidia on this system is the prebuilt linux-modules-nvidia-595-open package, built alongside the kernel rather than via DKMS, so it is not a working out-of-tree counter-example. There are no other DKMS modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: matt 5277 F.... wireplumber /dev/snd/controlC0: matt 5277 F.... wireplumber /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=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: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]

================================================================================ LINUX AUDIO FIX FOR HUAWEI AMD LAPTOPS ================================================================================ Author: Linux Community / Michael Lorentz Date: July 2026 Hardware: Huawei MateBook with AMD Ryzen processor (CX11970 audio codec) System: Linux Mint / Ubuntu / Other distributions with PipeWire ================================================================================ STEP-BY-STEP SOLUTION ================================================================================ PROBLEM DESCRIPTION: Audio on built-in laptop speakers does NOT work. Audio on headphones connected to the mini-jack DOES work. ================================================================================ STEP 1: CHECK AUDIO DEVICE STATUS ================================================================================ Open a terminal and run: $ pactl list short sinks If you see "SUSPENDED" status for the speaker device, this confirms the problem. Check if the sound card is detected: $ aplay -l You should see a card with the CX11970 codec (or similar). ================================================================================ STEP 2: IMMEDIATE AUDIO RESTORATION (QUICKEST METHOD) ================================================================================ Perform a full system restart: $ sudo reboot After restart, speaker audio should be restored. NOTE: If this doesn't work, proceed to Step 3. ================================================================================ STEP 3: MANUAL FIX (IF RESTART DID NOT HELP) ================================================================================ Run the following commands in the given order: $ sudo alsactl init $ sudo alsactl store $ systemctl --user restart pipewire pipewire-pulse $ pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo $ pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80% Test if audio works: $ speaker-test -t wav -c 2 ================================================================================ STEP 4: CHECK IF SPEAKERS ARE MUTED IN ALSA MIXER ================================================================================ $ alsamixer Press F6 and select your sound card (Generic_1 or CX11970). Check these channels: - Master - PCM - Speaker - Headphone If any shows "MM" (muted), press M on the keyboard to unmute. Use the arrow keys to set volume to approximately 80%. ================================================================================ STEP 5: AUTOMATIC STARTUP SCRIPT ================================================================================ To automate the fix at every system startup, create a script: $ mkdir -p ~/bin $ nano ~/bin/fix-audio.sh Paste the following content: ----------------------------------------------------------------------------- #!/bin/bash # Audio fix script for Huawei AMD sleep 30 # Reset ALSA sudo alsactl init 2>/dev/null # Restart PipeWire systemctl --user restart pipewire pipewire-pulse 2>/dev/null # Force speaker output pactl set-card-profile alsa_card.pci-0000_02_00.6 output:analog-stereo+input:analog-stereo 2>/dev/null pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo 2>/dev/null pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80% 2>/dev/null pactl set-sink-mute alsa_output.pci-0000_02_00.6.analog-stereo 0 2>/dev/null echo "$(date) - Audio fixed" >> /tmp/fix-audio.log ----------------------------------------------------------------------------- $ chmod +x ~/bin/fix-audio.sh ================================================================================ STEP 6: ADD SCRIPT TO AUTOSTART ================================================================================ $ nano ~/.config/autostart/fix-audio.desktop Paste (replace [USER] with your username): ----------------------------------------------------------------------------- [Desktop Entry] Type=Application Name=Fix Audio Exec=/home/[USER]/bin/fix-audio.sh Icon=audio-card X-GNOME-Autostart-enabled=true ----------------------------------------------------------------------------- ================================================================================ STEP 7: ALLOW SUDO WITHOUT PASSWORD (OPTIONAL) ================================================================================ To allow the script to run without asking for a password: $ sudo visudo -f /etc/sudoers.d/fix-audio Add (replace [USER] with your username): ----------------------------------------------------------------------------- [USER] ALL=(ALL) NOPASSWD: /home/[USER]/bin/fix-audio.sh ----------------------------------------------------------------------------- ================================================================================ STEP 8: DESKTOP SHORTCUT FOR QUICK FIX ================================================================================ Create a desktop shortcut to fix audio with one click: $ nano ~/Desktop/Fix-Audio.desktop Paste: ----------------------------------------------------------------------------- [Desktop Entry] Type=Application Name=Fix Audio Exec=gnome-terminal -- bash -c "sudo alsactl init; systemctl --user restart pipewire pipewire-pulse; pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo; pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80%; echo 'Audio fixed!'; read -p 'Press Enter'" Icon=audio-card Terminal=true ----------------------------------------------------------------------------- $ chmod +x ~/Desktop/Fix-Audio.desktop ================================================================================ STEP 9: RESET PIPEWIRE CONFIGURATION (IF OTHER METHODS FAIL) ================================================================================ If none of the above methods work, perform a full PipeWire reset: $ systemctl --user stop pipewire pipewire-pulse $ rm -rf ~/.config/pipewire $ rm -rf ~/.config/pulse $ rm -rf ~/.local/state/wireplumber $ rm -rf ~/.cache/pipewire $ systemctl --user start pipewire pipewire-pulse Then repeat Step 3. ================================================================================ STEP 10: INSTALL PAVUCONTROL (GRAPHICAL AUDIO MANAGEMENT TOOL) ================================================================================ $ sudo apt install pavucontrol Run: $ pavucontrol Go to the "Output Devices" tab: - Find the CX11970 device (or similar) - Click the green checkmark (Set as default) - In the "Port" dropdown, select "Speaker" instead of "Headphones" ================================================================================ DIAGNOSTICS - HOW TO CHECK WHAT'S WRONG ================================================================================ Check if the sound card is detected: $ aplay -l Check device status: $ pactl list short sinks Check available ports: $ pactl list cards | grep -A 20 "CX11970" Check kernel logs: $ dmesg | grep -i "snd\|audio\|hda" Check loaded modules: $ lsmod | grep snd ================================================================================ COMPARING "GOOD" AND "BAD" STATES ================================================================================ Save "good" state (when audio works): $ sudo cp -r /etc/modprobe.d /tmp/modprobe.d.good $ sudo cp -r /etc/modules-load.d /tmp/modules-load.d.good $ sudo cp -r /etc/pulse /tmp/pulse-system.good $ sudo cp -r /usr/share/pipewire /tmp/pipewire-share.good $ lsmod | grep snd > /tmp/snd-modules.good Save "bad" state (when audio does NOT work): $ sudo cp -r /etc/modprobe.d /tmp/modprobe.d.bad $ sudo cp -r /etc/modules-load.d /tmp/modules-load.d.bad $ sudo cp -r /etc/pulse /tmp/pulse-system.bad $ sudo cp -r /usr/share/pipewire /tmp/pipewire-share.bad $ lsmod | grep snd > /tmp/snd-modules.bad Compare states: $ diff -r /tmp/modprobe.d.good /tmp/modprobe.d.bad $ diff -r /tmp/modules-load.d.good /tmp/modules-load.d.bad $ diff -r /tmp/pulse-system.good /tmp/pulse-system.bad $ diff -r /tmp/pipewire-share.good /tmp/pipewire-share.bad $ diff /tmp/snd-modules.good /tmp/snd-modules.bad If diff shows no differences - the problem is in hardware registers. ================================================================================ WHAT DOES NOT WORK - WHAT NOT TO TRY ================================================================================ The following solutions have been tested and failed: | Method | Why It Failed | |--------|---------------| | Cron @reboot with delay | Runs too early | | Systemd service after sound.target | Runs before BIOS state is fully applied | | Disabling suspend in WirePlumber | Does not address hardware register state | | Blacklisting ACP modules | Does not reset hardware state | | Kernel parameters | Cannot override hardware register state | | Watchdog scripts | BIOS does not create configuration files | ================================================================================ ADDITIONAL INFORMATION - ROOT CAUSE OF THE PROBLEM ================================================================================ The problem occurs because BIOS/UEFI during initialization writes the audio controller state to hardware registers. Linux reads this state and applies it, which causes speakers to be marked as "unavailable." The state is stored in HARDWARE REGISTERS which: - Are not accessible via software tools - Are only reset during a full POST (Power-On Self-Test) - Are not dependent on configuration files This is why software solutions (scripts, file modifications) cannot fix the problem if the cause is in the hardware registers. ================================================================================ SUMMARY - MOST EFFECTIVE SOLUTIONS ================================================================================ 1. SYSTEM RESTART - always restores audio $ sudo reboot 2. MANUAL FIX - when restart doesn't help $ sudo alsactl init $ systemctl --user restart pipewire pipewire-pulse $ pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo 3. STARTUP SCRIPT - automate the fix Create ~/bin/fix-audio.sh and add to autostart 4. DESKTOP SHORTCUT - one-click quick fix ================================================================================ IMPORTANT NOTE - THE F12 / F2 BIOS ISSUE ================================================================================ During extensive testing, a critical discovery was made regarding how the problem is triggered: | BIOS Entry Method | Effect on Audio | |-------------------|-----------------| | F12 (boot device selection menu) | ❌ Speaker audio STOPS WORKING | | F2 (BIOS configuration / boot order) | ✅ Audio remains INTACT | THIS MEANS: - Entering BIOS itself is NOT the problem - The problem is the SPECIFIC hardware initialization mechanism used by F12 - If you need to change boot settings - use F2, not F12 HOW THIS WORKS: 1. BIOS/UEFI via F12 initializes the audio controller in a specific mode 2. This state is written to hardware registers 3. Linux reads and applies this state 4. The state causes speakers to be marked as "unavailable" 5. The system defaults to headphones as output RECOMMENDATION: - Avoid using F12 (boot menu) unless absolutely necessary - Use F2 (BIOS configuration) to change boot order - If you must use F12, perform a full restart without entering BIOS afterward -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2073049 Title: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression] Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: This laptop has had non-functioning internal sound (based on AMD Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in the kernel. Unfortunately, the sound is completely broken with kernel from package "linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers are not even listed in the sound GUI (I am using "mate-volume- control", with Ubuntu-Mate. When I boot the laptop on Linux 6.8.0-36-generic, the speakers are listed and the sound works normally. This might be related to this bug in Linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=218959 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/seq: julier 2643 F.... pipewire  /dev/snd/pcmC0D3p: julier 2643 F...m pipewire  /dev/snd/controlC0: julier 2645 F.... wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 14 11:03:18 2024 InstallationDate: Installed on 2022-04-18 (818 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220418) MachineType: HUAWEI HVY-WXX9 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:  linux-restricted-modules-6.8.0-38-generic N/A  linux-backports-modules-6.8.0-38-generic N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago) dmi.bios.date: 03/17/2023 dmi.bios.release: 2.17 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.17 dmi.board.asset.tag: N/A dmi.board.name: HVY-WXX9-PCB-B1 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.17 dmi.modalias: dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: HVY-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI [Impact] Huawei MateBook D14 AMD got no sound after commit: 4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check") which is introduced in v6.8.5 stable updates. [Fix] Invokes platform specific acp pin configuration check functions. Upstream fix: 09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure") [Test] Bug reporter tested on hardware, sound output OK. Also verified on ThinkPad T14 AMD, sound output OK too. [Where problems could occur] It may break sound output of AMD platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions

[Bug 2147556] Re: Logitech, Inc. HD Pro Webcam C920 no longer works

Solved in 7.0.0-29-generic ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147556 Title: Logitech, Inc. HD Pro Webcam C920 no longer works Status in linux package in Ubuntu: Fix Released Bug description: This logitech webcam has been working for years in Ubuntu. Something broke after kernel 6.11.11 : 046d:082d Logitech, Inc. HD Pro Webcam C920 I'm currently at 6.17.20.20. Somewhere in the interim there was one kernel that worked with this device, but all others kernels do not work. ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-20-generic 6.17.0-20.20 ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13 Uname: Linux 6.17.0-20-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: kms 5813 F.... wireplumber /dev/snd/controlC0: kms 5806 F.... pipewire kms 5813 F.... wireplumber /dev/snd/seq: kms 5806 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 18:23:34 2026 InstallationDate: Installed on 2021-10-12 (1639 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Latitude 7320 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=b5bc6390-52a3-4ffc-9214-018cf62caeb4 ro quiet splash i915.enable_psr=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 SourcePackage: linux UpgradeStatus: Upgraded to questing on 2025-11-03 (156 days ago) dmi.bios.date: 12/23/2025 dmi.bios.release: 1.45 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.45.0 dmi.board.name: 0TNW0H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.45.0:bd12/23/2025:br1.45:svnDellInc.:pnLatitude7320Detachable:pvr:rvnDellInc.:rn0TNW0H:rvrA01:cvnDellInc.:ct32:cvr:sku0A45: dmi.product.family: Latitude dmi.product.name: Latitude 7320 Detachable dmi.product.sku: 0A45 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-11-22T14:15:34.725524 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147556/+subscriptions

[Bug 2163551] [NEW] Intel Raptor Lake xHCI stalls with stale USB devices; USB input and external display freeze, i8042 keyboard also stops responding

Public bug reported: System: Ubuntu desktop on ASUS laptop Kernel: 7.0.0-29-generic Summary: During normal desktop use, USB input stopped functioning. The external USB keyboard and USB wireless mouse both stopped responding, while the built-in I2C touchpad continued to work. At approximately 2026-08-14 19:27 EDT I captured the system while it was in the failed state. The affected USB devices were still enumerated by lsusb and registered as Linux input devices with usbhid bound: - Intel Raptor Lake USB 3.2 Gen 2x2 xHCI controller: 0000:00:14.0 - USB wireless mouse: usb-0000:00:14.0-6, /dev/input/event12 - USB keyboard: usb-0000:00:14.0-1.2.4, /dev/input/event6 Both event devices remained present but produced no input events. Testing the raw event devices with: sudo timeout 10s od -An -tx1 /dev/input/event12 sudo timeout 10s od -An -tx1 /dev/input/event6 produced no data while moving/clicking the mouse or pressing keyboard keys. I then physically unplugged USB devices, including an external USB optical drive and other peripherals. The disconnected devices continued to appear in lsusb. This suggests that the kernel USB topology had become stale and disconnect events were no longer being processed. A second external monitor also froze, continuing to display its last image. The external displays are connected through a USB/USB-C HDMI adapter/dock. The built-in touchpad continued working throughout. It is an I2C HID device and is not connected through xHCI. Recovery test: I unbound and rebound the Intel xHCI controller: echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind sleep 3 echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind After rebinding xhci_hcd: - the USB mouse immediately worked again - USB devices could be reconnected normally - the external USB keyboard worked again - the previously frozen second monitor began working again However, the laptop's built-in keyboard remained nonfunctional. The built-in keyboard is separately registered as: AT Raw Set 2 keyboard /sys/devices/platform/i8042/serio0/ driver: /sys/bus/serio/drivers/atkbd It also produced no usable keyboard input. Unbinding and rebinding atkbd: echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/unbind sleep 2 echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/bind did NOT restore the laptop keyboard. The I2C touchpad remained functional. A search of the kernel journal during the failure for: i8042|serio|atkbd|keyboard|xhci|usb|hid|irq|interrupt|ACPI|timeout|error produced no messages. Expected result: USB devices should continue processing input and disconnect events. The built-in keyboard should remain functional. External displays should not freeze. Actual result: The Intel xHCI/USB path stopped processing input/disconnect activity while devices remained enumerated. An external display froze simultaneously. Resetting xhci_hcd restored the USB devices and external display, but the separate i8042/atkbd laptop keyboard remained nonfunctional. Additional observation: I have previously experienced external-display corruption when monitors are connected through the same USB/USB-C HDMI adapter/dock. I do not yet know whether those incidents have the same root cause, but I am including this as a potentially relevant correlation. Reproducibility: Not yet intentionally reproduced. This occurred during normal use with multiple USB peripherals/hubs and external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 19:43:44 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) WifiSyslog: dmi.bios.date: 10/24/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.320 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR 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.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.320:bd10/24/2024:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR 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 ** Attachment added: "full-journal.txt" https://bugs.launchpad.net/bugs/2163551/+attachment/5992266/+files/full-journal.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163551 Title: Intel Raptor Lake xHCI stalls with stale USB devices; USB input and external display freeze, i8042 keyboard also stops responding Status in linux package in Ubuntu: New Bug description: System: Ubuntu desktop on ASUS laptop Kernel: 7.0.0-29-generic Summary: During normal desktop use, USB input stopped functioning. The external USB keyboard and USB wireless mouse both stopped responding, while the built-in I2C touchpad continued to work. At approximately 2026-08-14 19:27 EDT I captured the system while it was in the failed state. The affected USB devices were still enumerated by lsusb and registered as Linux input devices with usbhid bound: - Intel Raptor Lake USB 3.2 Gen 2x2 xHCI controller: 0000:00:14.0 - USB wireless mouse: usb-0000:00:14.0-6, /dev/input/event12 - USB keyboard: usb-0000:00:14.0-1.2.4, /dev/input/event6 Both event devices remained present but produced no input events. Testing the raw event devices with: sudo timeout 10s od -An -tx1 /dev/input/event12 sudo timeout 10s od -An -tx1 /dev/input/event6 produced no data while moving/clicking the mouse or pressing keyboard keys. I then physically unplugged USB devices, including an external USB optical drive and other peripherals. The disconnected devices continued to appear in lsusb. This suggests that the kernel USB topology had become stale and disconnect events were no longer being processed. A second external monitor also froze, continuing to display its last image. The external displays are connected through a USB/USB-C HDMI adapter/dock. The built-in touchpad continued working throughout. It is an I2C HID device and is not connected through xHCI. Recovery test: I unbound and rebound the Intel xHCI controller: echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind sleep 3 echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind After rebinding xhci_hcd: - the USB mouse immediately worked again - USB devices could be reconnected normally - the external USB keyboard worked again - the previously frozen second monitor began working again However, the laptop's built-in keyboard remained nonfunctional. The built-in keyboard is separately registered as: AT Raw Set 2 keyboard /sys/devices/platform/i8042/serio0/ driver: /sys/bus/serio/drivers/atkbd It also produced no usable keyboard input. Unbinding and rebinding atkbd: echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/unbind sleep 2 echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/bind did NOT restore the laptop keyboard. The I2C touchpad remained functional. A search of the kernel journal during the failure for: i8042|serio|atkbd|keyboard|xhci|usb|hid|irq|interrupt|ACPI|timeout|error produced no messages. Expected result: USB devices should continue processing input and disconnect events. The built-in keyboard should remain functional. External displays should not freeze. Actual result: The Intel xHCI/USB path stopped processing input/disconnect activity while devices remained enumerated. An external display froze simultaneously. Resetting xhci_hcd restored the USB devices and external display, but the separate i8042/atkbd laptop keyboard remained nonfunctional. Additional observation: I have previously experienced external-display corruption when monitors are connected through the same USB/USB-C HDMI adapter/dock. I do not yet know whether those incidents have the same root cause, but I am including this as a potentially relevant correlation. Reproducibility: Not yet intentionally reproduced. This occurred during normal use with multiple USB peripherals/hubs and external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 19:43:44 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) WifiSyslog: dmi.bios.date: 10/24/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.320 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR 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.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.320:bd10/24/2024:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR 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/2163551/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-6.8/6.8.0-1067.75~22.04.1)

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