** 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/2167170 Title: Lenovo IdeaPad 3 15ALC6 (82KU): fan RPM unavailable because yogafan driver is not enabled Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo IdeaPad 3 15ALC6 DMI product_name: 82KU DMI product_version: IdeaPad 3 15ALC6 Kernel: 7.0.0-31-generic Problem: The system fan works normally under firmware/EC control, but its RPM is not exposed through Linux hwmon/lm-sensors. Observed: $ modinfo yogafan modinfo: ERROR: Module yogafan not found. $ grep CONFIG_SENSORS_YOGAFAN /boot/config-$(uname -r) CONFIG_SENSORS_YOGAFAN is not present. Current hwmon devices: ADP0 BAT0 nvme k10temp amdgpu No fan*_input or PWM interface is exposed. Upstream Linux includes the yogafan hwmon driver and Lenovo IdeaPad 3 15ALC6 (82KU) is listed as supported hardware. Expected: With yogafan support enabled, fan RPM should be exposed through the standard hwmon interface (fan*_input) and become visible to tools such as lm-sensors. Request: Please consider enabling or backporting CONFIG_SENSORS_YOGAFAN for Ubuntu kernels supporting this hardware. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sat Sep 12 16:08:26 2026 InstallationDate: Installed on 2026-08-18 (25 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: LENOVO 82KU ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=59aa6ae4-acbd-4b71-9752-4627997b9853 ro video=HDMI-A-1:1920x1080@60e 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: 03/19/2025 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN68WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76466WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ALC6 dmi.ec.firmware.release: 1.60 dmi.modalias: dmi:bvnLENOVO:bvrGLCN68WW:bd03/19/2025:br1.68:efr1.60:svnLENOVO:pn82KU:pvrIdeaPad315ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ALC6:skuLENOVO_MT_82KU_BU_idea_FM_IdeaPad315ALC6:pfaIdeaPad315ALC6: dmi.product.family: IdeaPad 3 15ALC6 dmi.product.name: 82KU dmi.product.sku: LENOVO_MT_82KU_BU_idea_FM_IdeaPad 3 15ALC6 dmi.product.version: IdeaPad 3 15ALC6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167170/+subscriptions
суббота
[Bug 2167177] Re: Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci
** 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/2167177 Title: Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci Status in linux package in Ubuntu: New Bug description: On a MacBook8,1 (2016 12" MacBook, Intel Broadwell), the internal SPI keyboard and trackpad intermittently fail to initialize at boot. A restart always resolves the issue. The failure is caused by a race between dw_dmac_pci and pxa2xx_spi_pci module probe order. Symptoms: Intermittent: keyboard and trackpad not detected after boot (no input: Apple SPI Keyboard / input: Apple SPI Touchpad in dmesg) Restart always fixes it No external keyboard required to reproduce (it's a boot-time race) Root Cause: The spi_pxa2xx_pci driver checks for DMA channel availability at probe time. The outcome depends on whether dw_dmac_pci has already registered its channels: Good boot: pxa2xx_spi_pci probes first → "no DMA channels available, using PIO" → works Bad boot: dw_dmac_pci probes first → SPI sees DMA → uses DMA → transfers time out (-110) → driver re-queues a message still linked in the SPI core's list → list corruption (__list_add_valid_or_report warning) → driver is permanently stuck Failed boot log (kernel 7.0.0-31-generic): dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error reading from device: -110 WARNING: lib/list_debug.c:35 at __list_add_valid_or_report+0xc6/0xe0, CPU#3: spi1/455 spi_queued_transfer+0xed/0x110 __spi_async+0xd5/0x160 spi_async+0xd6/0xe0 applespi_send_cmd_msg+0x17d/0x400 [applespi] applespi_msg_complete+0xc5/0x110 [applespi] applespi_async_read_complete+0x5c/0x60 [applespi] spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 Successful boot log (same kernel, same machine): pxa2xx_spi_pci 0000:00:15.4: no DMA channels available, using PIO dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: Received corrupted packet (crc mismatch) applespi spi-APP000D:00: modeswitch done. input: Apple SPI Touchpad as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input5 Upstream Status: The list-corruption bug (re-queueing applespi->wr_m via spi_async() while still linked in SPI core lists) was identified in the sashiko- bot review of the v4/v5 patch series (Shih-Yuan Lee, July 2026, linux- spi mailing list). The same series adds a force_pio module parameter to spi_pxa2xx_pci as a workaround. Workaround (untested, for reference): # /etc/modprobe.d/spi-force-pio.conf options spi_pxa2xx_pci force_pio=1 (Requires the upstream patch to be applied; the parameter does not exist in 7.0.0-31-generic.) System: Ubuntu 24.04.1 LTS Kernel: 7.0.0-31-generic Hardware: MacBook8,1 (Intel Core M, Broadwell) SPI controller: Intel LPSS at 00:15.4 DMA controller: DesignWare at 00:15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167177/+subscriptions
[Bug 2167152] Re: Monitor does not turn on after hibernate
** 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/2167152 Title: Monitor does not turn on after hibernate Status in linux package in Ubuntu: New Bug description: after the computer is suspended, pressing a key on the keyboard turns on the computer and mouse, but the monitor stays turned off. pressing more keys or moving the mouse does not turn on the monitor. switching back one version to linux-image-6.8.0-138-generic resolves the issue. thank you ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-138.138-generic 6.8.12 Uname: Linux 6.8.0-138-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 23:31:25 2026 InstallationDate: Installed on 2023-06-20 (1180 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Gigabyte Technology Co., Ltd. B650 AORUS ELITE AX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-138-generic root=UUID=f690b9fb-6c9f-43b2-8833-8576a984803d 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-138-generic N/A linux-backports-modules-6.8.0-138-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F42c dmi.board.asset.tag: Default string dmi.board.name: B650 AORUS ELITE AX dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF42c:bd07/21/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnB650AORUSELITEAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650AORUSELITEAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B650 MB dmi.product.name: B650 AORUS ELITE AX dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167152/+subscriptions
[Bug 2167160] Re: [HawkPoint1 1002:1900] gfx_0.0.0 timeout, failed MES ring reset, then GNOME Shell SIGABRT and session loss
** 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/2167160 Title: [HawkPoint1 1002:1900] gfx_0.0.0 timeout, failed MES ring reset, then GNOME Shell SIGABRT and session loss Status in linux package in Ubuntu: New Bug description: Suggested package: linux (Ubuntu), Ubuntu 26.04 / Resolute. Two AMDGPU hangs on this laptop ended the GNOME Wayland login session while the kernel continued running. The second occurred during ordinary terminal use, despite a previously installed Ptyxis Cairo-renderer workaround. ## System - Lenovo IdeaPad Slim 5 16AHP9, product 83DD; BIOS NGCN34WW, dated 2026-01-16. - AMD HawkPoint1, PCI 1002:1900 (rev cc), subsystem 17aa:3807; amdgpu. - Ubuntu 26.04.1 LTS; kernel 7.0.0-31-generic, Ubuntu package 7.0.0-31.31 (base 7.0.14). - GNOME Shell 50.1-0ubuntu1.2; Mutter 50.1-0ubuntu2.2; Wayland. - Mesa / mesa-libgallium 26.0.8-1ubuntu0.3; Ptyxis 50.1-1ubuntu2. - AMD firmware: linux-firmware-amd-graphics 20260319.git217ca6e4-0ubuntu3.1. - Internal eDP panel only at inspection time; boot log reports PSR support 0. - No amdgpu overrides appear in the kernel command line. GPU performance policy is auto; ppfeaturemask is 0xfff7bfff. These versions match the released Ubuntu archive as checked on 2026-09-12. Package integrity verification reported no discrepancies for Mesa Gallium, Mesa DRI/Vulkan, libdrm-amdgpu, Mutter, Shell and AMD graphics firmware. ## What happened On 2026-09-12 at 10:27:02 UTC, the graphics ring timed out, naming GNOME Shell PID 10699 and its graphics-submission thread 10716. MES did not respond to RESET and then repeatedly failed REMOVE_QUEUE. A MODE2 GPU reset succeeded at 10:27:31. GNOME Shell reported loss of an innocent graphics context and aborted. At 10:27:39 systemd recorded status 6/ABRT for the Shell service; Ptyxis lost its Wayland compositor connection. The login session ended at 10:27:41, and a new login began at 10:28:22. The kernel did not reboot; its boot began on 2026-09-11 at 16:20:43 UTC. No preceding GPU page fault, DMCUB/flip timeout, kernel OOM kill or systemd-oomd kill was found in the inspected logs for this incident. A previous event on 2026-09-11 at 12:03:49 UTC, on the same kernel version, named Ptyxis in its gfx_0.0.0 timeout and also required a GPU reset. ## Symbolized Shell backtrace The crashing thread is LWP 10716, matching the submission thread named in the timeout. Matching Ubuntu Mesa debug symbols were selected by build ID b089ec2f62ded38e9327502246aa4ccfb7929b24: ``` abort() amdgpu_ctx_set_sw_reset_status() at amdgpu_cs.cpp:491 amdgpu_cs_submit_ib<(queue_type)0>() at amdgpu_cs.cpp:2113 util_queue_thread_func() at u_queue.c:294 impl_thrd_routine() at threads_posix.c:43 ``` The matching Mesa 26.0.8 source identifies line 2113 as the -ECANCELED / PIPE_INNOCENT_CONTEXT_RESET path. The subsequent abort explains the session loss. It does not establish what originally hung the graphics ring. ## Trigger and mitigation already tried The user was working with Codex CLI in Ptyxis when the second event occurred. There is no reliable reproduction command, and Codex is not established as the cause. These are two observed incidents, not a controlled reproduction. After the first incident, a user-local Ptyxis wrapper selected GSK_RENDERER=cairo and a D-Bus override routed desktop activation through it. Both were installed before the next boot. After the second incident and new login, the running Ptyxis process had GSK_RENDERER=cairo and no open /dev/dri/ handles. The closed terminal's environment cannot be checked retrospectively. The workaround's installation has therefore not established system stability. Enabled Shell extensions at inspection time: ``` monitor@astraext.github.io ding@rastersoft.com snapd-prompting@canonical.com snapd-search-provider@canonical.com tiling-assistant@ubuntu.com ubuntu-appindicators@ubuntu.com ubuntu-dock@ubuntu.com web-search-provider@ubuntu.com ``` A comparison with extensions disabled has not been performed. Neither has a newer/mainline kernel test. The GPU device coredump expired before it was saved. Selected journals and the symbolized userspace backtrace are attached. ## Related reports and requested next step These reports have related symptoms but are not established duplicates: - https://gitlab.freedesktop.org/mesa/mesa/-/work_items/15668 — same GPU family and graphics-ring/MES recovery signature, with a different game trigger. - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158614 — innocent-context abort and session loss, on a different GPU with preceding Chrome page faults. Ubuntu Proposed currently has kernel 7.0.0-38.38, whose changelog includes AMD gfx11 queue-interrupt fixes. Is that the appropriate next comparison for this hardware, or should the next step be a specific Mesa/firmware test or additional diagnostics? No particular fix or initiating defect is claimed. This report was prepared with AI assistance from the user's local journals and existing crash dump. Raw process environments and memory dumps are not included in the attached text. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167160/+subscriptions
[Bug 2167163] Re: System boot loop / instantly returns to login page after a restart on kernel 7.0.0-30System boot loop / instantly returns to login page after a restart on kernel 7.0.0-30
** 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/2167163 Title: System boot loop / instantly returns to login page after a restart on kernel 7.0.0-30System boot loop / instantly returns to login page after a restart on kernel 7.0.0-30 Status in linux package in Ubuntu: New Bug description: Problem Description: The desktop session abruptly crashes and forces me back to the GDM/login screen. There is no rigid pattern, but it consistently triggers when multitasking with resource-heavy or graphical applications under Linux kernel 7.0.0-30-generic. It frequently occurs when opening: - Zoom + VS Code + Terminal simultaneously. - Zoom + VS Code, followed by launching Counter-Strike 2 (CS2). Hardware Environment (Current Desktop): 32 GB RAM AMD RYZEN 5 7640hs 1 TB SSD AMD RADEON graphics Additional Hardware Verification: Note for developers: I have verified that this exact same issue also occurs under identical conditions on my Acer Swift 3 laptop, which runs the following hardware: - CPU: AMD Ryzen 7 5000 Series - GPU: AMD Radeon Graphics - RAM: 16 GB Steps to Reproduce: 1. Boot into the desktop session using kernel 7.0.0-30. 2. Launch combinations of Zoom, VS Code, and a terminal window, or launch Zoom, VS Code, and CS2. 3. The display frozen briefly or immediately crashes, dropping the user session straight back to the login screen. Expected Behavior: The desktop environment should manage the window composition, application load, and graphical rendering without terminating the user session. Actual Behavior: The graphical display server crashes instantly back to the login screen, losing all unsaved work. 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.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 12 15:37:15 2026 InstallationDate: Installed on 2026-08-26 (17 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: BOSGAME LIMITED P3 MIX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=e5b5bc83-c3fc-4caa-a774-a3e007d110ed 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: 08/06/2025 dmi.bios.release: 1.11 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.11 dmi.board.asset.tag: Default string dmi.board.name: ARB19D dmi.board.vendor: BOSGAME LIMITED dmi.board.version: Version 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: SU dmi.chassis.version: Default string dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.11:bd08/06/2025:br1.11:efr1.1:svnBOSGAMELIMITED:pnP3MIX:pvrVersion1.0:rvnBOSGAMELIMITED:rnARB19D:rvrVersion1.0:cvnSU:ct35:cvrDefaultstring:sku0003:pfaARB19D: dmi.product.family: ARB19D dmi.product.name: P3 MIX dmi.product.sku: 0003 dmi.product.version: Version 1.0 dmi.sys.vendor: BOSGAME LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167163/+subscriptions
[Bug 2142384] Re: ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz) on Ubuntu 24.04 kernel 6.17
Launchpad has imported 13 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=220854. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://documentation.ubuntu.com/launchpad/user/reference/bugs/multi-project-bugs/about-multi-project-bugs/#bugs-in-external-trackers. ------------------------------------------------------------------------ On 2025-12-12T00:42:34+00:00 passelaigue.florian wrote: Summary: The stylus on HP OmniBook X Flip 14-fm0xxx is laggy and misses inputs under Linux. The touchscreen works perfectly fine (finger input), only the stylus is affected. The stylus works flawlessly under Windows 11, confirming this is not a hardware issue. The kernel logs show repeated "i2c_hid_get_input: incomplete report (67/5631)" errors when using the stylus. The device 04F3:442A is not in the explicit device list for hid-multitouch and is handled by the generic alias "hid:b*g0004v*p*". Hardware: - Laptop: HP OmniBook X Flip Laptop 14-fm0xxx - CPU: Intel Core Ultra 7 258V (Lunar Lake) - BIOS: Insyde F.08 (2025-08-18) - Digitizer: ELAN2514:00 04F3:442A (I2C HID) - Stylus: MPP 2.0 compatible pen Software: - Distro: CachyOS (Arch-based) - Kernel tested: 6.12.60-2-cachyos-lts and 6.18.0-3-cachyos - Desktop: GNOME on Wayland Issue details: When using the stylus, input is laggy and some strokes are missed or delayed. The kernel spams the following error in dmesg: i2c_hid_acpi i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/5631) The driver expects 5631 bytes but only receives 67 bytes per report. Notable observations from boot logs: - Device creates multiple input nodes including several "UNKNOWN" types - Initial "IRQ triggered but there's no data" message at boot - Device is handled by hid-multitouch via generic alias, not device-specific match Steps to reproduce: 1. Boot Linux on HP OmniBook X Flip 14-fm0xxx 2. Use any MPP 2.0 stylus on the touchscreen 3. Observe laggy input and check dmesg for "incomplete report" errors === HID DEVICE INFO === $ cat /sys/bus/hid/devices/0018:04F3:442A.0003/uevent DRIVER=hid-multitouch HID_ID=0018:000004F3:0000442A HID_NAME=ELAN2514:00 04F3:442A HID_PHYS=i2c-ELAN2514:00 HID_UNIQ= MODALIAS=hid:b0018g0004v000004F3p0000442A === HID REPORT DESCRIPTOR (base64, 1173 bytes) === BQ0JBKEBhQEFDQkioQIJQhUAJQF1AZUBgQJ1AYEDdQUJUSU/gQJ1AQlHJQGBAqQm/wB1CFUPZRE2 AABG/wAJSIECCUmBApUBBQEmEA51EFUPZREJMDUARi4BlQKBAibQCEa9AAkxgQK0wAUNCSKhAglC FQAlAXUBlQGBAnUBgQN1BQlRJT+BAnUBCUclAYECpCb/AHUIVQ9lETYAAEb/AAlIgQIJSYEClQEF ASYQDnUQVQ9lEQkwNQBGLgGVAoECJtAIRr0ACTGBArTABQ0JIqECCUIVACUBdQGVAYECdQGBA3UF CVElP4ECdQEJRyUBgQKkJv8AdQhVD2URNgAARv8ACUiBAglJgQKVAQUBJhAOdRBVD2URCTA1AEYu AZUCgQIm0AhGvQAJMYECtMAFDQkioQIJQhUAJQF1AZUBgQJ1AYEDdQUJUSU/gQJ1AQlHJQGBAqQm /wB1CFUPZRE2AABG/wAJSIECCUmBApUBBQEmEA51EFUPZREJMDUARi4BlQKBAibQCEa9AAkxgQK0 wAUNCSKhAglCFQAlAXUBlQGBAnUBgQN1BQlRJT+BAnUBCUclAYECpCb/AHUIVQ9lETYAAEb/AAlI gQIJSYEClQEFASYQDnUQVQ9lEQkwNQBGLgGVAoECJtAIRr0ACTGBArTABQ0JVlUAZQAn////f5UB dSCBAglUJX+VAXUIgQKFCglVJQqxAoVEBgD/CcUVACb/AHUIlgABsQLABv8BCQGhAYUCFQAm/wB1 CJVACQCBAsAGAP8JAaEBhQN1CJUgCQGRAsAFDQkCoQGFBzUACSChAAkyCUIJRAk8CUUJWhUAJQF1 AZUGgQKVAoEDBQEJMHUQlQGkVQ9lEUYuASYAS4FCCTFGvQAmAC+BQrQFDQkwJgAQgQJ1CJUBCTsm /wCBQnUQlQEJPaRlFFUONtjcRigjFtjcJigjgQIJPoECNQBHoIwAABUAJ6CMAAAJP4ECtAlWVQxm ARAn//8AAEf//wAAlgEAdRCBAgYA/3UIlQIJAYECwMAGAP8JgaEBhRd1CJVACQWBAsB1CBUAJv8A Bgv/CQuhAZUCCUiFSLEClQ8JKYUpsQKVHwkqhSqxApU+CSuFK7EClf4JLIUssQKW/gEJLYUtsQKV DwkuhS6BApUfCS+FL4EClT4JMIUwgQKV/gkxhTGBApb+AQkyhTKBApb+AwkzhTOBApb+Bwk0hTSB Apb+Dwk1hTWBApY/HQk2hTaBAsAGD/8JYKEBhRl1CJUEFQAm/wAJAJEChRl1CJUEFQAm/wAJxoEC wAYP/wlQoQGFInUglQEXAAAAgCf///9/CXKBAglzgQIJdIECCXWBAsAFAQkGoQGFEQUHGeAp5xUA JQF1AZUIgQKVA3UIFQAlcBkAKXCBAMAFDAkBoQGFEgnpCeoJ4gnNFQAlAXUBlQSBApUcgQPABQEJ AqEBhRMJAaEABQkZASkFFQAlAXUBlQWBApUDgQMFAQkwCTEJOBWBJX91CJUDgQbAwAYE/wnzoQGF RRUAJv8AdQiVHwn1gQLABgT/CfShAYVGdQiVIAn2kQLA === BOOT LOGS (relevant excerpt) === i2c_hid_acpi i2c-ELAN2514:00: i2c_hid_get_input: IRQ triggered but there's no data input: ELAN2514:00 04F3:442A Touchscreen as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input11 input: ELAN2514:00 04F3:442A as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input12 input: ELAN2514:00 04F3:442A Stylus as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input13 input: ELAN2514:00 04F3:442A UNKNOWN as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input27 input: ELAN2514:00 04F3:442A UNKNOWN as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input30 input: ELAN2514:00 04F3:442A UNKNOWN as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input31 input: ELAN2514:00 04F3:442A UNKNOWN as /devices/pci0000:00/0000:00:19.0/i2c_designware.2/i2c-2/i2c-ELAN2514:00/0018:04F3:442A.0003/input/input32 hid-multitouch 0018:04F3:442A.0003: input,hidraw2: I2C HID v1.00 Keyboard [ELAN2514:00 04F3:442A] on i2c-ELAN2514:00 [When using stylus:] i2c_hid_acpi i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/5631) i2c_hid_acpi i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/5631) [...repeated many times...] === LIBINPUT INFO === Device: ELAN2514:00 04F3:442A Stylus Kernel: /dev/input/event12 Id: i2c:04f3:442a Group: 8 Seat: seat0, default Size: 300x188mm Capabilities: tablet === LOADED MODULES === $ lsmod | grep -E "hid|multitouch" hid_multitouch 36864 0 i2c_hid_acpi 12288 0 i2c_hid 49152 1 i2c_hid_acpi Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/0 ------------------------------------------------------------------------ On 2026-03-11T20:56:26+00:00 lr6183286 wrote: I want to add that this is also affecting the HP Omnibook 7 Flip 16t-au000 with same outputs as the bug report had presented. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/5 ------------------------------------------------------------------------ On 2026-05-19T02:45:50+00:00 glen wrote: Ditto for HP Omnibook X 16-as0043dx, except that the stylus is device 04F3:43F0 and the incomplete reports are 67/7167. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/7 ------------------------------------------------------------------------ On 2026-05-19T02:49:29+00:00 glen wrote: Oops, sorry for incomplete report: This is on Manjaro Linux, under both Xorg and Sway/Wayland (but not Windows), kernel 6.18.26 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/8 ------------------------------------------------------------------------ On 2026-05-19T04:12:48+00:00 glen wrote: Don't mean to spam here, just wanted to report that I did just update to kernel 7.0.9 and the problem persists. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/9 ------------------------------------------------------------------------ On 2026-08-14T20:03:38+00:00 godfatherjohn wrote: I have got this issue, too. Kernel 7.1.8, Fedora 44, Genome, HP Omnibook 16 2-in-1, model: 16-as0xxxx Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/11 ------------------------------------------------------------------------ On 2026-08-31T14:46:09+00:00 stani.m wrote: # uname -r: 7.2.0-1-cachyos # sudo dmidecode -s system-product-name: HP OmniBook X Flip 14 # sudo dmidecode -s bios-version: F.20 # sudo dmidecode -s bios-release-date: 04/27/2026 # fwupdmgr get-updates: Devices without available firmware updates The issue is reproducible with two different compatible pens, including a Lenovo Slim Pen. Both produce the identical i2c_hid_get_input: incomplete report (67/5631) error. Touch input works normally; only stylus input is affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/12 ------------------------------------------------------------------------ On 2026-08-31T18:45:52+00:00 godfatherjohn wrote: https://bugzilla.kernel.org/show_bug.cgi?id=221612 <-- this is the same issue/ a related issue, I believe. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/13 ------------------------------------------------------------------------ On 2026-09-02T17:43:40+00:00 godfatherjohn wrote: Apparently, mrmoe12 on Launchpad has proposed -- better is to say "made a fix" -- tailored for Ubuntu-based distros. Maybe this is something to start from. https://github.com/perryFile/hp-elan2514-pen-fix I haven't tried the fix myself since my HP runs Fedora. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/17 ------------------------------------------------------------------------ On 2026-09-02T17:44:27+00:00 godfatherjohn wrote: The thread on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/18 ------------------------------------------------------------------------ On 2026-09-02T20:53:24+00:00 stani.m wrote: fix works for me on cachyos k7.2.2. https://github.com/BitSlice32/hp-elan2514-pen-fix-cachy-k7.2 Had to add my ELAN device to list. ELAN2514:00 04F3:4428 Stylus ELAN2514:00 04F3:442A Stylus << my device. Message still appears: [ 4570.464976] i2c_hid_acpi i2c-ELAN2514:00: i2c_hid_get_input: incomplete report (67/5631) Tested with HP Stylus and Lenovo Slim pen. No more lag with xournal++ and Pinta, at least. Thx @perryFile and @godfatherjohn Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/20 ------------------------------------------------------------------------ On 2026-09-03T20:18:42+00:00 godfatherjohn wrote: Created attachment 310778 proposed fix works but needs standardisation https://github.com/BitSlice32/hp-elan2514-pen-fix-cachy-k7.2 Original investigation and solution by https://github.com/perryFile/hp-elan2514-pen-fix Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/21 ------------------------------------------------------------------------ On 2026-09-12T00:20:43+00:00 maclyn wrote: To add another data point: On an HP OmniBook Flip 16" (16-au0773cl) with the same vendor/product ID as reported by Glen above (04F3:43F0), the fix from perryFile modified to the specific digitizer product ID of that notebook (43F0) works well. As BitSlice reports, there are still sporadic "incomplete report (67/xxxx)" logs, but the frequency drops from dozens of times/second to <10/second, the stylus feels responsive, and the touchscreen no longer stops responding after sustained stylus input (this was reported elsewhere, and was the case for me without the patch). Tested with the HP MPP 2.0 Tilt Pen included with my device on kernel-7.2.4-200.fc44/KDE in Krita. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/comments/24 ** Changed in: linux (Fedora) Status: Unknown => Confirmed ** Changed in: linux (Fedora) Importance: Unknown => Medium ** Bug watch added: Linux Kernel Bug Tracker #221612 https://bugzilla.kernel.org/show_bug.cgi?id=221612 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142384 Title: ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz) on Ubuntu 24.04 kernel 6.17 Status in linux package in Ubuntu: Fix Released Status in linux package in Fedora: Confirmed Bug description: The active stylus on my HP OmniBook x Flip Ultra 14 reports at extremely low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with kernel 6.17.0-14-generic. The pen input is choppy and unusable, while touch input works normally. The pen is a HP MPP tilt pen 2.0 Steps to Reproduce: Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14. Ensure kernel 6.17.0-14-generic is in use. Run: sudo libinput debug-events And then i move the pen and compare the input events with touch on my screen. The timestamps of the pen are 40-100 ms apart, which makes it unusable. I think this is the stylus in libinput: Device: ELAN2514:00 04F3:4428 Stylus Kernel: /dev/input/event7 Group: 5 Seat: seat0, default Size: 300x188mm Capabilities: tablet Accel profiles: none Other relevant info: lsmod | grep hid hid_sensor_prox 20480 0 hid_sensor_trigger 20480 3 hid_sensor_prox hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf intel_hid 32768 0 sparse_keymap 12288 2 hp_wmi,intel_hid mac_hid 12288 0 hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox usbhid 77824 0 hid_multitouch 36864 0 hid_generic 12288 0 i2c_hid_acpi 12288 0 i2c_hid 40960 1 i2c_hid_acpi hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control on Ubuntu 24.04.4 LTS Kernel: 6.17.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/+subscriptions
[Bug 2167177] [NEW] Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci
Public bug reported: On a MacBook8,1 (2016 12" MacBook, Intel Broadwell), the internal SPI keyboard and trackpad intermittently fail to initialize at boot. A restart always resolves the issue. The failure is caused by a race between dw_dmac_pci and pxa2xx_spi_pci module probe order. Symptoms: Intermittent: keyboard and trackpad not detected after boot (no input: Apple SPI Keyboard / input: Apple SPI Touchpad in dmesg) Restart always fixes it No external keyboard required to reproduce (it's a boot-time race) Root Cause: The spi_pxa2xx_pci driver checks for DMA channel availability at probe time. The outcome depends on whether dw_dmac_pci has already registered its channels: Good boot: pxa2xx_spi_pci probes first → "no DMA channels available, using PIO" → works Bad boot: dw_dmac_pci probes first → SPI sees DMA → uses DMA → transfers time out (-110) → driver re-queues a message still linked in the SPI core's list → list corruption (__list_add_valid_or_report warning) → driver is permanently stuck Failed boot log (kernel 7.0.0-31-generic): dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error reading from device: -110 WARNING: lib/list_debug.c:35 at __list_add_valid_or_report+0xc6/0xe0, CPU#3: spi1/455 spi_queued_transfer+0xed/0x110 __spi_async+0xd5/0x160 spi_async+0xd6/0xe0 applespi_send_cmd_msg+0x17d/0x400 [applespi] applespi_msg_complete+0xc5/0x110 [applespi] applespi_async_read_complete+0x5c/0x60 [applespi] spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 Successful boot log (same kernel, same machine): pxa2xx_spi_pci 0000:00:15.4: no DMA channels available, using PIO dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: Received corrupted packet (crc mismatch) applespi spi-APP000D:00: modeswitch done. input: Apple SPI Touchpad as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input5 Upstream Status: The list-corruption bug (re-queueing applespi->wr_m via spi_async() while still linked in SPI core lists) was identified in the sashiko-bot review of the v4/v5 patch series (Shih-Yuan Lee, July 2026, linux-spi mailing list). The same series adds a force_pio module parameter to spi_pxa2xx_pci as a workaround. Workaround (untested, for reference): # /etc/modprobe.d/spi-force-pio.conf options spi_pxa2xx_pci force_pio=1 (Requires the upstream patch to be applied; the parameter does not exist in 7.0.0-31-generic.) System: Ubuntu 24.04.1 LTS Kernel: 7.0.0-31-generic Hardware: MacBook8,1 (Intel Core M, Broadwell) SPI controller: Intel LPSS at 00:15.4 DMA controller: DesignWare at 00:15.0 ** 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/2167177 Title: Intermittent SPI keyboard/trackpad failure at boot — DMA/PIO module load order race in spi_pxa2xx_pci Status in linux package in Ubuntu: New Bug description: On a MacBook8,1 (2016 12" MacBook, Intel Broadwell), the internal SPI keyboard and trackpad intermittently fail to initialize at boot. A restart always resolves the issue. The failure is caused by a race between dw_dmac_pci and pxa2xx_spi_pci module probe order. Symptoms: Intermittent: keyboard and trackpad not detected after boot (no input: Apple SPI Keyboard / input: Apple SPI Touchpad in dmesg) Restart always fixes it No external keyboard required to reproduce (it's a boot-time race) Root Cause: The spi_pxa2xx_pci driver checks for DMA channel availability at probe time. The outcome depends on whether dw_dmac_pci has already registered its channels: Good boot: pxa2xx_spi_pci probes first → "no DMA channels available, using PIO" → works Bad boot: dw_dmac_pci probes first → SPI sees DMA → uses DMA → transfers time out (-110) → driver re-queues a message still linked in the SPI core's list → list corruption (__list_add_valid_or_report warning) → driver is permanently stuck Failed boot log (kernel 7.0.0-31-generic): dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error reading from device: -110 WARNING: lib/list_debug.c:35 at __list_add_valid_or_report+0xc6/0xe0, CPU#3: spi1/455 spi_queued_transfer+0xed/0x110 __spi_async+0xd5/0x160 spi_async+0xd6/0xe0 applespi_send_cmd_msg+0x17d/0x400 [applespi] applespi_msg_complete+0xc5/0x110 [applespi] applespi_async_read_complete+0x5c/0x60 [applespi] spi_master spi1: failed to transfer one message from queue applespi spi-APP000D:00: SPI transfer timed out applespi spi-APP000D:00: Error writing to device: -110 Successful boot log (same kernel, same machine): pxa2xx_spi_pci 0000:00:15.4: no DMA channels available, using PIO dw_dmac_pci 0000:00:15.0: DesignWare DMA Controller, 8 channels input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input4 applespi spi-APP000D:00: Received corrupted packet (crc mismatch) applespi spi-APP000D:00: modeswitch done. input: Apple SPI Touchpad as /devices/pci0000:00/0000:00:15.4/spi_master/spi1/spi-APP000D:00/input/input5 Upstream Status: The list-corruption bug (re-queueing applespi->wr_m via spi_async() while still linked in SPI core lists) was identified in the sashiko- bot review of the v4/v5 patch series (Shih-Yuan Lee, July 2026, linux- spi mailing list). The same series adds a force_pio module parameter to spi_pxa2xx_pci as a workaround. Workaround (untested, for reference): # /etc/modprobe.d/spi-force-pio.conf options spi_pxa2xx_pci force_pio=1 (Requires the upstream patch to be applied; the parameter does not exist in 7.0.0-31-generic.) System: Ubuntu 24.04.1 LTS Kernel: 7.0.0-31-generic Hardware: MacBook8,1 (Intel Core M, Broadwell) SPI controller: Intel LPSS at 00:15.4 DMA controller: DesignWare at 00:15.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167177/+subscriptions
[Bug 1849953] Re: Kernel Oops: 0002 [#1] SMP PTI - kernel NULL pointer dereference; RIP is at 0010:queue_work_on+0x1b/0x50
I can relate to the frustration of dealing with an issue that does not happen consistently. I faced a similar situation while working on https://checknolbalance.ae/ where an issue appeared only occasionally, which made it much harder to reproduce and troubleshoot. Those intermittent problems are honestly the worst because everything can look perfectly normal during testing, then suddenly fail when you least expect it. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1849953 Title: Kernel Oops: 0002 [#1] SMP PTI - kernel NULL pointer dereference; RIP is at 0010:queue_work_on+0x1b/0x50 Status in linux package in Ubuntu: Expired Bug description: The kernel oops seems to happen when the laptop is left idle. It doesn't appear every time, so it is hard to reproduce. System is completely unresponsive after it and hard reboot is needed. I also observed identical freezes on Ubuntu 19.04, but never bothered to fill a bug report. I haven't observed this error on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: david 1625 F.... pulseaudio /dev/snd/pcmC0D0p: david 1625 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 13:53:07 2019 InstallationDate: Installed on 2019-10-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LW0010GE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=20db2748-18f3-45cc-b013-010ae1b24637 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware 1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET57W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LW0010GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LW0010GE:pvrThinkPadL580:rvnLENOVO:rn20LW0010GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L580 dmi.product.name: 20LW0010GE dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580 dmi.product.version: ThinkPad L580 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849953/+subscriptions
пятница
[Bug 2167015] Re: System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD
** Description changed: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - - Working: 6.17.0-40-generic, 6.17.0-35-generic (both shut down cleanly every time) + - Working: 6.17.0-40-generic (shuts down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux - on the broken kernel did not help and even caused reboot to hang as - well. + on the broken kernel did not help. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. ** Summary changed: - System hangs on poweroff since kernel 7.0.0 series (regression) on ThinkPad L14 Gen1 AMD + System hangs on poweroff since kernel 7.0.0 series (regression) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167015 Title: System hangs on poweroff since kernel 7.0.0 series (regression) Status in linux package in Ubuntu: New Bug description: Since upgrading to kernel 7.0.0-28-generic (and confirmed also in 7.0.0-30 and 7.0.0-31), my system no longer powers off cleanly. This is a clear regression: kernel 6.17.0-40-generic works reliably on the exact same hardware/install. Hardware: Lenovo ThinkPad L14 Gen 1 AMD (Type 20U5/20U6), AMD Ryzen 5 PRO 4650U, BIOS R19ET56W (1.40). Distro: Linux Mint (based on Ubuntu 24.04 / noble, HWE kernel stack) Symptom: When shutting down, all systemd services stop cleanly and the log reaches "Reached target poweroff.target", "Syncing filesystems and block devices", "Sending SIGTERM to remaining processes" - then the journal stops. The screen goes black, but the fans keep spinning and the power LED stays on. The system never actually powers off; it requires a hard power-button hold to turn off. Tested and confirmed: - Broken: 7.0.0-28-generic, 7.0.0-30-generic, 7.0.0-31-generic - Working: 6.17.0-40-generic (shuts down cleanly every time) No custom kernel parameters were needed on the working kernels (default "quiet splash"). Testing with acpi=force / reboot=acpi / acpi_osi=Linux on the broken kernel did not help. This looks like a regression in ACPI/power-management handling introduced somewhere between 6.17.0-40 and 7.0.0-28. Steps to reproduce: 1. Boot into kernel 7.0.0-31-generic (or 7.0.0-28/30) 2. Run "sudo poweroff" or shut down via the desktop menu 3. Observe: screen turns black, fans keep running, power LED stays on, system never actually powers off Expected result: System powers off completely. Actual result: System hangs indefinitely until a hard power-button shutdown is performed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167015/+subscriptions
[Bug 2167148] [NEW] Bluetooth (MediaTek MT7922) fails to initialize with NULL pointer dereference in btmtk_setup_firmware_79xx on 6.8.0-139-generic; works on 6.8.0-138-generic
Public bug reported: SUMMARY On kernel 6.8.0-139-generic, the Bluetooth controller on a MediaTek MT7922 Wi-Fi/Bluetooth combo adapter fails to initialize. The kernel throws a NULL pointer dereference during firmware setup, hci0 never comes up, and `bluetoothctl` reports "No default controller available" even though rfkill shows the device as present and unblocked. Booting the previous point release, 6.8.0-138-generic, with no other changes, fixes the issue completely — Bluetooth initializes normally and the controller powers on. HARDWARE - Adapter: MediaTek MT7922 802.11ax PCIe Wi-Fi + Bluetooth combo (lspci: "04:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter", driver mt7921e) - Bluetooth HCI: hci0, driver btusb/btmtk - Laptop: Framework 15 AFFECTED / WORKING KERNELS - Broken: 6.8.0-139-generic (6.8.0-139.139) - Working: 6.8.0-138-generic (6.8.0-138.138) STEPS TO REPRODUCE 1. Boot 6.8.0-139-generic 2. Run `rfkill list` — hci0 shows present, not soft/hard blocked 3. Run `systemctl status bluetooth` — service is active/running 4. Run `bluetoothctl show` — reports "No default controller available" 5. Attempt to enable Bluetooth from GNOME Settings — toggle does not turn on / has no effect 6. Check `sudo dmesg | grep -A30 btmtk_setup_firmware_79xx` — shows a kernel oops with a NULL pointer dereference (see trace below) EXPECTED BEHAVIOR Bluetooth controller initializes normally and can be enabled from Settings, as it does on 6.8.0-138-generic. ACTUAL BEHAVIOR Kernel oops during hci_power_on -> btmtk firmware setup, controller never registers with BlueZ. KERNEL OOPS (6.8.0-139-generic) [ 4.747120] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20250523103438 [ 4.747142] Workqueue: hci0 hci_power_on [bluetooth] [ 4.747201] btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] [ 4.747204] ? __pfx_btmtk_usb_hci_wmt_sync+0x10/0x10 [btmtk] [ 4.747207] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] [ 4.747212] btusb_mtk_setup+0x453/0x610 [btusb] [ 4.747218] hci_dev_setup_sync+0x6c/0x430 [bluetooth] [ 4.747241] ? __pm_runtime_idle+0x4c/0xd0 [ 4.747244] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] [ 4.747278] hci_dev_open_sync+0xb1/0x350 [bluetooth] [ 4.747318] hci_dev_do_open+0x28/0x70 [bluetooth] [ 4.747352] hci_power_on+0x50/0x210 [bluetooth] [ 4.747398] process_one_work+0x181/0x3a0 [ 4.747404] worker_thread+0x18b/0x330 [ 4.747412] kthread+0xef/0x120 [ 4.747420] ret_from_fork+0x44/0x70 [ 4.747428] ret_from_fork_asm+0x1b/0x30 [ 4.747435] </TASK> [ 4.747574] CR2: 0000000000000219 [ 4.747578] ---[ end trace 0000000000000000 ]--- [ 5.002337] mt7921e 0000:04:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250523103150a [ 5.109748] mt7921e 0000:04:00.0: WM Firmware Version: ____000000, Build Time: 20250523103234 Note CR2 = 0x219, a small offset from NULL — consistent with a NULL struct pointer being dereferenced with a field offset inside btmtk_setup_firmware_79xx / btmtk_usb_hci_wmt_sync. Also note the Bluetooth and Wi-Fi halves of the chip both print firmware version info at boot; the Wi-Fi half (mt7921e) succeeds while the Bluetooth half (btmtk) crashes. This may point to a race or shared resource issue between the two drivers on this combo chip. ADDITIONAL SYMPTOM While investigating, running `sudo modprobe -r btusb` on the affected kernel (6.8.0-139-generic) hung indefinitely in an uninterruptible state (did not respond to Ctrl+C), suggesting the driver may leave a lock or work item in a bad state after the initial oops. WORKAROUND Booting 6.8.0-138-generic instead of 6.8.0-139-generic resolves the issue with no other changes. Reinstalling linux-firmware and rebooting on 6.8.0-139-generic did NOT resolve it, suggesting this is a kernel/ driver regression rather than a firmware blob issue. ADDITIONAL INFO $ lspci -k | grep -A3 -i network 04:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter Kernel driver in use: mt7921e Kernel modules: mt7921e $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-138-generic 6.8.0-138.138 ProcVersionSignature: Ubuntu 6.8.0-138.138-generic 6.8.12 Uname: Linux 6.8.0-138-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: plaba 4379 F.... wireplumber /dev/snd/controlC0: plaba 4379 F.... wireplumber /dev/snd/controlC1: plaba 4379 F.... wireplumber /dev/snd/seq: plaba 4375 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 22:37:14 2026 InstallationDate: Installed on 2021-12-11 (1736 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-138-generic root=UUID=0cd2207b-af42-4735-8148-fa96decb31f3 ro security=selinux quiet splash intel_iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 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-138-generic N/A linux-backports-modules-6.8.0-138-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2026-02-21 (202 days ago) dmi.bios.date: 12/22/2025 dmi.bios.release: 4.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 04.03 dmi.board.asset.tag: * dmi.board.name: FRANMZCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRAGACCPA744840005 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr04.03:bd12/22/2025:br4.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRAGACCP07: dmi.product.family: 16in Laptop dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series) dmi.product.sku: FRAGACCP07 dmi.product.version: A7 dmi.sys.vendor: Framework modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2023-04-23T16:21:23.712186 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167148 Title: Bluetooth (MediaTek MT7922) fails to initialize with NULL pointer dereference in btmtk_setup_firmware_79xx on 6.8.0-139-generic; works on 6.8.0-138-generic Status in linux package in Ubuntu: New Bug description: SUMMARY On kernel 6.8.0-139-generic, the Bluetooth controller on a MediaTek MT7922 Wi-Fi/Bluetooth combo adapter fails to initialize. The kernel throws a NULL pointer dereference during firmware setup, hci0 never comes up, and `bluetoothctl` reports "No default controller available" even though rfkill shows the device as present and unblocked. Booting the previous point release, 6.8.0-138-generic, with no other changes, fixes the issue completely — Bluetooth initializes normally and the controller powers on. HARDWARE - Adapter: MediaTek MT7922 802.11ax PCIe Wi-Fi + Bluetooth combo (lspci: "04:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter", driver mt7921e) - Bluetooth HCI: hci0, driver btusb/btmtk - Laptop: Framework 15 AFFECTED / WORKING KERNELS - Broken: 6.8.0-139-generic (6.8.0-139.139) - Working: 6.8.0-138-generic (6.8.0-138.138) STEPS TO REPRODUCE 1. Boot 6.8.0-139-generic 2. Run `rfkill list` — hci0 shows present, not soft/hard blocked 3. Run `systemctl status bluetooth` — service is active/running 4. Run `bluetoothctl show` — reports "No default controller available" 5. Attempt to enable Bluetooth from GNOME Settings — toggle does not turn on / has no effect 6. Check `sudo dmesg | grep -A30 btmtk_setup_firmware_79xx` — shows a kernel oops with a NULL pointer dereference (see trace below) EXPECTED BEHAVIOR Bluetooth controller initializes normally and can be enabled from Settings, as it does on 6.8.0-138-generic. ACTUAL BEHAVIOR Kernel oops during hci_power_on -> btmtk firmware setup, controller never registers with BlueZ. KERNEL OOPS (6.8.0-139-generic) [ 4.747120] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20250523103438 [ 4.747142] Workqueue: hci0 hci_power_on [bluetooth] [ 4.747201] btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] [ 4.747204] ? __pfx_btmtk_usb_hci_wmt_sync+0x10/0x10 [btmtk] [ 4.747207] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] [ 4.747212] btusb_mtk_setup+0x453/0x610 [btusb] [ 4.747218] hci_dev_setup_sync+0x6c/0x430 [bluetooth] [ 4.747241] ? __pm_runtime_idle+0x4c/0xd0 [ 4.747244] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] [ 4.747278] hci_dev_open_sync+0xb1/0x350 [bluetooth] [ 4.747318] hci_dev_do_open+0x28/0x70 [bluetooth] [ 4.747352] hci_power_on+0x50/0x210 [bluetooth] [ 4.747398] process_one_work+0x181/0x3a0 [ 4.747404] worker_thread+0x18b/0x330 [ 4.747412] kthread+0xef/0x120 [ 4.747420] ret_from_fork+0x44/0x70 [ 4.747428] ret_from_fork_asm+0x1b/0x30 [ 4.747435] </TASK> [ 4.747574] CR2: 0000000000000219 [ 4.747578] ---[ end trace 0000000000000000 ]--- [ 5.002337] mt7921e 0000:04:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250523103150a [ 5.109748] mt7921e 0000:04:00.0: WM Firmware Version: ____000000, Build Time: 20250523103234 Note CR2 = 0x219, a small offset from NULL — consistent with a NULL struct pointer being dereferenced with a field offset inside btmtk_setup_firmware_79xx / btmtk_usb_hci_wmt_sync. Also note the Bluetooth and Wi-Fi halves of the chip both print firmware version info at boot; the Wi-Fi half (mt7921e) succeeds while the Bluetooth half (btmtk) crashes. This may point to a race or shared resource issue between the two drivers on this combo chip. ADDITIONAL SYMPTOM While investigating, running `sudo modprobe -r btusb` on the affected kernel (6.8.0-139-generic) hung indefinitely in an uninterruptible state (did not respond to Ctrl+C), suggesting the driver may leave a lock or work item in a bad state after the initial oops. WORKAROUND Booting 6.8.0-138-generic instead of 6.8.0-139-generic resolves the issue with no other changes. Reinstalling linux-firmware and rebooting on 6.8.0-139-generic did NOT resolve it, suggesting this is a kernel/ driver regression rather than a firmware blob issue. ADDITIONAL INFO $ lspci -k | grep -A3 -i network 04:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter Kernel driver in use: mt7921e Kernel modules: mt7921e $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-138-generic 6.8.0-138.138 ProcVersionSignature: Ubuntu 6.8.0-138.138-generic 6.8.12 Uname: Linux 6.8.0-138-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: plaba 4379 F.... wireplumber /dev/snd/controlC0: plaba 4379 F.... wireplumber /dev/snd/controlC1: plaba 4379 F.... wireplumber /dev/snd/seq: plaba 4375 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 22:37:14 2026 InstallationDate: Installed on 2021-12-11 (1736 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-138-generic root=UUID=0cd2207b-af42-4735-8148-fa96decb31f3 ro security=selinux quiet splash intel_iommu=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 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-138-generic N/A linux-backports-modules-6.8.0-138-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2026-02-21 (202 days ago) dmi.bios.date: 12/22/2025 dmi.bios.release: 4.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 04.03 dmi.board.asset.tag: * dmi.board.name: FRANMZCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRAGACCPA744840005 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr04.03:bd12/22/2025:br4.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRAGACCP07: dmi.product.family: 16in Laptop dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series) dmi.product.sku: FRAGACCP07 dmi.product.version: A7 dmi.sys.vendor: Framework modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2023-04-23T16:21:23.712186 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167148/+subscriptions
[Bug 2156644] Re: GNOME Panel & Activities Overview workspace thumbnails flickering issue
Ever since 7.0.0.30 was rolled out I have not had this issue occur, perhaps it is due to the kernel itself or other system updates that were rolled out along with it. 7.0.0.31 also does not have this issue, so I'm assuming the issue was addressed by the kernel update or system updates, but after several reboots and fresh starts using the newer kernels the problem has vanished for me. I didn't do any other configuration changes as I was relying on my script to mitigate the issue but since 7.0.0.30 my script hasn't executed once and I have gone days and days without any issues. Laying my script to rest and moving on with life as usual. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: Fix Released Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 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-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
[Bug 2156644] Re: GNOME Panel & Activities Overview workspace thumbnails flickering issue
Ever since 7.0.0.30 was rolled out I have not had this issue occur, perhaps it is due to the kernel itself or other system updates that were rolled out along with it. 7.0.0.31 also does not have this issue. ** 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/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: Fix Released Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 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-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
[Bug 2166998] Re: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701)
** Tags added: linux-firmware-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166998 Title: No sound from internal speakers on ASUS ExpertBook P5406CCA (ALC294, subsystem 0x10433701) Status in linux package in Ubuntu: Confirmed Status in linux-firmware-misc package in Ubuntu: Confirmed Bug description: speakers silent while HDMI, Bluetooth and headphone jack work; audio worked under Windows; subsystem ID 0x10433701; dmesg showing speaker_outs=0 with the generic driver; mixer unmuted with Auto-Mute disabled; and the workarounds that failed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: alsa-base 1.0.25+dfsg-0ubuntu9 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ajit 4051 F.... pipewire ajit 4064 F.... wireplumber /dev/snd/seq: ajit 4051 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:42:10 2026 InstallationDate: Installed on 2026-09-06 (4 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK P5406CCA PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 5.32 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: P5406CCA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P5406CCA 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: 2.11 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrP5406CCA.203:bd03/20/2026:br5.32:efr2.11:svnASUS:pnASUSEXPERTBOOKP5406CCA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP5406CCA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK P5406CCA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166998/+subscriptions