The output for your command is: linux-firmware: Installed: 20240318.git3b128b60.0ubuntu3.1 Candidate: 20240318.git3b128b60.0ubuntu3.1 Version table: *** 20240318.git3b128b60.0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble-updates/main i386 Packages 100 /var/lib/dpkg/status 20240318.git3b128b60-0ubuntu2.26 500 500 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages 20240318.git3b128b60-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167190 Title: [amdgpu][Navi 31] Reboot hangs on HWE 7.0; 6.17 works; blocking amdgpu avoids hang Status in linux package in Ubuntu: New Bug description: # Probable AMDGPU-related reboot regression on Ubuntu HWE 7.0 Prepared locally on 2026-09-13. Tested on Linux Mint 22.3 using Ubuntu-provided kernels. This has not yet been reproduced on an Ubuntu installation. ## Summary On Linux Mint 22.3 (Ubuntu 24.04 base), restarting with Ubuntu HWE kernel 7.0 can leave the screen off and fans running/ramping, requiring a power-button reset. Kernel 6.17.0-40 has restarted successfully with graphics enabled and is the current workaround. Normal power-off and restart directly from BIOS have also worked. The strongest comparison is between two text-mode boots of the same 7.0.0-31 kernel: reboot hung with Intel graphics blocked and AMDGPU initialized; reboot succeeded after additionally blocking AMDGPU. This strongly implicates the AMDGPU initialization/shutdown path or its interaction with other kernel components. It does not establish the exact defective function or commit. A malformed earlier blacklist test reportedly restarted with Intel still loaded, so intermittency remains possible. ## Environment - Linux Mint 22.3, Ubuntu noble base, x86_64. - Working installed kernel: 6.17.0-40-generic, package 6.17.0-40.40~24.04.1. - Failing kernel: 7.0.0-31-generic, package 7.0.0-31.31~24.04.1, upstream version reported as 7.0.14. - Also reported failing: 7.0.0-28 and 7.0.0-30. - Discrete GPU: AMD Navi 31, PCI ID 1002:744c, ASRock subsystem 1849:5308. PCI naming covers RX 7900 XT/XTX variants; exact retail model not established here. - Integrated GPU: Intel Alder Lake-S GT1, PCI ID 8086:4680, i915 driver under normal operation. - Motherboard: MSI PRO Z690-A WIFI (MS-7D25). - BIOS: A.D0, dated 2023-07-10. ## Tests and evidence | Test | Boot configuration | Reported result | | --- | --- | --- | | Installed 6.17.0-40 | Normal graphical boot | Reboot worked | | Mint live USB, 6.14.0-37 | Live desktop | Reboot worked | | 7.0.0-31 | Normal desktop | Reboot hung | | 7.0.0-31 | `systemd.unit=multi-user.target` | Reboot hung; LightDM did not start | | 7.0.0-31 | `systemd.unit=multi-user.target nomodeset` | Reboot worked | | Test B, 7.0.0-31 | `systemd.unit=multi-user.target module_blacklist=i915,xe` | Latest test hung | | Test C, 7.0.0-31 | `systemd.unit=multi-user.target module_blacklist=i915,xe,amdgpu` | Reboot worked | Test B on September 13 at 10:26 CDT recorded: ```text Module i915 is blacklisted Module xe is blacklisted [drm] Initialized amdgpu 3.64.0 for 0000:03:00.0 on minor 1 ``` Test C on September 13 at 10:33 CDT recorded: ```text Module i915 is blacklisted Module xe is blacklisted Module amdgpu is blacklisted ``` The preserved journal reaches the final systemd shutdown stage and stops when journald terminates. No preserved stack trace identifies the hang. Reaching reboot.target or seeing Journal stopped alone does not prove a reboot succeeded; success/failure outcomes above come from the user's physical observations. Earlier 7.0 boots logged AMD display REG_WAIT timeouts, but those messages alone do not establish the cause. A temporary EFI reset- method test also hung. Current measurements taken during normal operation did not show overheating; temperatures during the actual hang were not captured. ## Current workaround GRUB defaults to 6.17.0-40-generic with normal graphics drivers enabled. The kernel image and module packages are marked manually installed. Kernel updates remain enabled, but newly installed kernels will not automatically replace this explicit default. Local configuration: - `/etc/default/grub.d/99-working-kernel.cfg`: working default and five-second menu. - `/etc/grub.d/42_reboot_diagnostics`: optional tests A, B, C. Do not use the all-GPU blacklist or nomodeset as the normal daily boot configuration if GPU acceleration is required. ## Suggested maintainer follow-up Review as an AMDGPU-related regression between 6.17 and 7.0. Identify a relevant fixed distribution kernel or request targeted late-shutdown traces. Repeat the B/C comparison if needed because the failure may be intermittent. Further isolation should be based on maintainer guidance rather than changing unrelated BIOS settings or disabling broad power- management features. Related reports found during research involve other AMD hardware and do not establish that the same defect or fix applies here. No specific published fix was verified for this machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167190/+subscriptions
воскресенье
[Bug 2167076] Re: Automatic screen rotation does not apply despite valid IIO accelerometer events
** Package changed: mutter (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167076 Title: Automatic screen rotation does not apply despite valid IIO accelerometer events Status in linux package in Ubuntu: New Bug description: Surface Go 2 on Ubuntu 26.04 Resolute, Wayland. Automatic rotation is enabled: org.gnome.settings-daemon.peripherals.touchscreen orientation-lock = false Mutter reports: PanelOrientationManaged = true HasExternalMonitor = false Display transform remains normal (0). iio-sensor-proxy 3.8 reports HasAccelerometer=true and emits normal, right-up, and left-up orientation changes through monitor-sensor. Restarting the GNOME session did not restore automatic display rotation. Versions: mutter 50.1-0ubuntu2.2 gnome-shell 50.1-0ubuntu1.2 linux-image-7.0.0-31-generic 7.0.0-31.31 The regression was noticed after moving from 7.0.0-30 to 7.0.0-31. The relevant HID sensor-hub module changed; ISH transport and HID 3D accelerometer modules did not. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: mutter (not installed) 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 19:23:31 2026 InstallationDate: Installed on 2025-11-04 (311 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: mutter UpgradeStatus: Upgraded to resolute on 2026-08-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167076/+subscriptions
[Bug 2167076] [NEW] Automatic screen rotation does not apply despite valid IIO accelerometer events
You have been subscribed to a public bug: Surface Go 2 on Ubuntu 26.04 Resolute, Wayland. Automatic rotation is enabled: org.gnome.settings-daemon.peripherals.touchscreen orientation-lock = false Mutter reports: PanelOrientationManaged = true HasExternalMonitor = false Display transform remains normal (0). iio-sensor-proxy 3.8 reports HasAccelerometer=true and emits normal, right-up, and left-up orientation changes through monitor-sensor. Restarting the GNOME session did not restore automatic display rotation. Versions: mutter 50.1-0ubuntu2.2 gnome-shell 50.1-0ubuntu1.2 linux-image-7.0.0-31-generic 7.0.0-31.31 The regression was noticed after moving from 7.0.0-30 to 7.0.0-31. The relevant HID sensor-hub module changed; ISH transport and HID 3D accelerometer modules did not. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: mutter (not installed) 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 11 19:23:31 2026 InstallationDate: Installed on 2025-11-04 (311 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: mutter UpgradeStatus: Upgraded to resolute on 2026-08-29 (12 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- Automatic screen rotation does not apply despite valid IIO accelerometer events https://bugs.launchpad.net/bugs/2167076 You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2167202] [NEW] thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails
Public bug reported: A bus-powered JHL7440 Thunderbolt enclosure containing an AQC113 spontaneously disconnects on both USB4 ports. The Thunderbolt device reconnects, but its PCI hierarchy is not restored reliably. In one captured recovery the AQC113 appeared after bridge-window allocation, received no BAR resources, and failed probe with error -5. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus resized the bridge windows and restored 10GbE without rebooting. GEEKOM A7 Max, BIOS 1.26 Ubuntu and 7.0.0-31-generic Wavlink WL-NWU342G, JHL7440, NVM 69.84 AQC113 firmware 1.5.48 Both USB4 ports affected 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 13 16:17:22 2026 InstallationDate: Installed on 2026-08-15 (29 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: GEEKOM A7 Max ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash pcie_aspm.policy=performance iommu=pt pci=nocrs pcie_port_pm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 09/15/2025 dmi.bios.release: 1.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.26 dmi.board.asset.tag: Default string dmi.board.name: A7 Max dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.26:bd09/15/2025:br1.26:efr1.3:svnGEEKOM:pnA7Max:pvrDefaultstring:rvnDefaultstring:rnA7Max:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuGEEKOMA7Max:pfaA...MaxSeries: dmi.product.family: A...Max Series dmi.product.name: A7 Max dmi.product.sku: GEEKOM A7 Max dmi.product.version: Default string dmi.sys.vendor: GEEKOM ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute ** Attachment added: "hardware and package versions, topology, spontaneous failure, BAR-allocation failure," https://bugs.launchpad.net/bugs/2167202/+attachment/5999969/+files/ubuntu-thunderbolt-aqc113-bug-report.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167202 Title: thunderbolt/pci JHL7440/AQC113 fails to recover after tunnel disconnect; BAR allocation fails Status in linux package in Ubuntu: New Bug description: A bus-powered JHL7440 Thunderbolt enclosure containing an AQC113 spontaneously disconnects on both USB4 ports. The Thunderbolt device reconnects, but its PCI hierarchy is not restored reliably. In one captured recovery the AQC113 appeared after bridge-window allocation, received no BAR resources, and failed probe with error -5. Removing the complete JHL7440 PCI subtree and rescanning the empty parent bus resized the bridge windows and restored 10GbE without rebooting. GEEKOM A7 Max, BIOS 1.26 Ubuntu and 7.0.0-31-generic Wavlink WL-NWU342G, JHL7440, NVM 69.84 AQC113 firmware 1.5.48 Both USB4 ports affected 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 13 16:17:22 2026 InstallationDate: Installed on 2026-08-15 (29 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: GEEKOM A7 Max ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash pcie_aspm.policy=performance iommu=pt pci=nocrs pcie_port_pm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 09/15/2025 dmi.bios.release: 1.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.26 dmi.board.asset.tag: Default string dmi.board.name: A7 Max dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.26:bd09/15/2025:br1.26:efr1.3:svnGEEKOM:pnA7Max:pvrDefaultstring:rvnDefaultstring:rnA7Max:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuGEEKOMA7Max:pfaA...MaxSeries: dmi.product.family: A...Max Series dmi.product.name: A7 Max dmi.product.sku: GEEKOM A7 Max dmi.product.version: Default string dmi.sys.vendor: GEEKOM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167202/+subscriptions
[Bug 2167197] Re: Cannot control screen brightness
** 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/2167197 Title: Cannot control screen brightness Status in linux package in Ubuntu: New Bug description: Include: HP Spectre X360 Converaible Product# W2Q33AV BIOS F.55 Intel HD Graphics 520 (8086:1916). Ubuntu Cinnamon 26.04.1. Kernel versions 7.0.0-30 and 7.0.0-31. /sys/class/backlight/intel_backlight exists. brightnessctl changes 234/937 to 796/937. The hardware panel’s brightness does not change. nomodeset removal successfully enabled i915 but did not restore functional backlight control. I worked this situation using Perplexity and ended up here. The keyboard does change the OSD value but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: max 2042 F.... wireplumber /dev/snd/seq: max 2038 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Sun Sep 13 13:52:54 2026 InstallationDate: Installed on 2026-04-25 (141 days ago) InstallationMedia: Ubuntu-Cinnamon 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: HP HP Spectre x360 Convertible 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-31-generic root=UUID=048998cb-c0da-42a1-acfa-55e74d7e24c9 ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2020 dmi.bios.release: 15.55 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.55 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.79 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.79 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.55:bd06/29/2020:br15.55:efr33.79:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.79:cvnHP:ct31:cvrChassisVersion:skuW2Q33AV:pfa103C_5335KVG=NL=CONB=HPS=SPT: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.product.sku: W2Q33AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167197/+subscriptions
суббота
[Bug 2152056] Re: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152056 Title: Lenovo Legion Y9000P IAX10 (17aa:3907) speakers - missing AW88399 amp quirk Status in linux package in Ubuntu: Confirmed Bug description: Lenovo Legion Y9000P IAX10, ALC287 + AW88399 amplifier PCI SSID: 17aa:3907 dmesg: "ALC287: picked fixup for PCI SSID 17aa:0000" (no specific quirk match) Result: bottom 2 speakers (woofers) silent, only top tweeters audible Existing patch (not yet upstream): https://github.com/nadimkobeissi/16iax10h-linux-sound-saga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152056/+subscriptions
[Bug 2167170] Re: Lenovo IdeaPad 3 15ALC6 (82KU): fan RPM unavailable because yogafan driver is not enabled
** 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