Two more recurrences on 2026-09-06 on 7.0.0-31-generic (MGLRU still disabled: /sys/kernel/mm/lru_gen/enabled -> 0x0000). **#8 — 2026-09-06 08:53 JST** - Oops: page fault (not-present page) at lru_activate+0x91/0x3e0 - Comm: kworker/15:0 (Workqueue: events mmput_async_fn), UID 0 - Path: mmput_async_fn -> exit_mmap -> folio_mark_accessed -> lru_activate - Same RIP as my 2026-08-23 report (lru_activate) but triggered from async mm teardown, not a read syscall. **#9 — 2026-09-06 08:59 JST** (kdump reboot ~6 min after #8) - Oops: general protection fault at __page_cache_release.part.0+0xac/0x240 - Comm: V8Worker (PID 8551, UID 1000) — Cursor/Electron V8 worker - Path: do_madvise -> __page_cache_release -> folios_put_refs - Same class as 2026-08-30 (Comm: cursor, madvise path). Hardware unchanged: ASUS PRIME Z690M-PLUS D4, 64GB RAM, RTX 5060 Ti, nvidia OE. Not OOM. Full kdump dmesg archived locally; excerpt attached. Recurrence table update: | Date (JST) | Kernel | RIP | Comm | |-------------------|----------|-----------------------------|-----------------| | 2026-09-06 08:53 | 7.0.0-31 | lru_activate | kworker/15:0 | | 2026-09-06 08:59 | 7.0.0-31 | __page_cache_release | V8Worker | Still awaiting 7.0.0-32+ with upstream MGLRU fixes. ** Attachment added: "kdump dmesg excerpt 2026-09-06 (#8 and #9)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162722/+attachment/5997821/+files/launchpad_2162722_kdump_dmesg_20260906.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162722 Title: general protection fault in lru_gen_del_folio during exit_mmap (ThreadPoolForeg) Status in linux package in Ubuntu: New Bug description: DistroRelease: Ubuntu 26.04 LTS (resolute) Package: linux-image-7.0.0-28-generic 7.0.0-28.28 Kernel: Linux 7.0.0-28-generic #28-Ubuntu SMP PREEMPT_DYNAMIC x86_64 Hardware: ASUS PRIME Z690M-PLUS D4, BIOS 3811 GPU: NVIDIA GeForce RTX 5060 Ti (driver 610.43.02, tainted OE) Impact of the bug: The entire system rebooted unexpectedly (kdump). Work in progress was lost. What I expected to happen: The desktop session should remain stable under normal application load. What actually happened: On 2026-08-03 ~17:25 JST, during heavy Electron/Chromium workload (Cursor IDE agent/plan build), the kernel hit an Oops and kdump triggered an automatic reboot. kdump artifacts: /var/crash/202608031725/ (dmesg + vmcore) Apport ticket: cb836c7a-8f1f-11f1-8811-9953c338e1ca Kernel Oops (from kdump dmesg): Oops: general protection fault, probably for non-canonical address 0xffff7127d16b6d48: 0000 [#1] SMP NOPTI CPU: 6 PID: 80704 Comm: ThreadPoolForeg Tainted: G OE (nvidia out-of-tree modules loaded) RIP: lru_gen_del_folio.constprop.0+0x19a/0x380 Call Trace: lru_gen_del_folio __page_cache_release.part.0 folios_put_refs free_pages_and_swap_cache zap_pte_range exit_mmap do_exit get_signal Not OOM: 64 GB RAM, swap unused at time of crash. Correlating load (not proven causal): - GNOME localsearch indexing CIFS/rclone/SSHFS mounts under ~/drive and ~/mnt - CIFS automount retries to unreachable //192.168.1.152/ (return code -113/-4) Host mitigations already applied locally: - localsearch ignored-directories: drive, mnt - Disabled unreachable .152 CIFS fstab automount Regression notes: Similar sudden reboots were rare on Ubuntu 24.04 (6.8 kernel). This is the first kdump on 26.04 / 7.0.0-28-generic on this machine. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ytsubame 2780 F.... wireplumber /dev/snd/controlC0: ytsubame 2780 F.... wireplumber /dev/snd/seq: ytsubame 2696 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 18:39:40 2026 InstallationDate: Installed on 2026-07-13 (21 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS System Product Name PackageArchitecture: amd64 ProcEnviron: LANG=ja_JP.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=dumb XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=9061133c-3778-49ec-85ba-ecb208384534 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: general protection fault in lru_gen_del_folio during exit_mmap (ThreadPoolForeg) UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 10/22/2025 dmi.bios.release: 38.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3811 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3811:bd10/22/2025:br38.11:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162722/+subscriptions
суббота
[Bug 2166509] Re: NULL pointer dereference in btmtk_usb_hci_wmt_sync kills MT7925 Bluetooth in 6.8.0-139 (regression from 6.8.0-138)
Hi, thought I'd chime in, also affected. Knocked out the BT chip of my Framework 16. Attaching more information to the ticket in case it helps. Similar disclosure as OP, the comment below comes from Claude Code/Opus 4.8. --- Independent reproduction on MediaTek MT7922 (Framework "RZ616"), confirming this is not MT7925-specific. HARDWARE - Framework Laptop 16 (AMD Ryzen 7040 Series) - Bluetooth: MT7922 USB 0e8d:e616 (btusb + btmtk). Wi-Fi side is mt7921e (PCIe) and is unaffected. - Ubuntu noble SAME REGRESSION BOUNDARY AS REPORTED (from my journal, 10 boots): - 6.8.0-138.138 -- Bluetooth initializes normally. Aug 21 - Sep 2, 7 boots, no oops, valid BD address. - 6.8.0-139.139 -- crashes on every boot. Sep 5, 3 boots. Controller left DOWN INIT with address 00:00:00:00:00:00. BT firmware is identical on both kernels (Build Time: 20250523103438); only the kernel differs. OOPS ON 6.8.0-139 (matches the reported __pm_runtime_resume(NULL) mechanism): BUG: kernel NULL pointer dereference, address: 0000000000000219 Oops: 0000 [#1] PREEMPT SMP NOPTI Workqueue: hci0 hci_power_on [bluetooth] RIP: 0010:__pm_runtime_resume+0x1b/0x80 Call Trace: btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] btusb_mtk_setup+0x453/0x610 [btusb] hci_dev_setup_sync+0x6c/0x430 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0xb1/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] WORKAROUND CONFIRMED: booting 6.8.0-138 restores internal Bluetooth. (A USB CSR dongle also works, since it doesn't go through btusb_mtk_setup().) This confirms the report's "MT7921/MT7922/MT7925 all affected" statement on real MT7922 hardware and a second platform (Framework Laptop 16, vs. the original MSI desktop). Full 6.8.0-139 dmesg attached. ** Attachment added: "lp2166509-mt7922-dmesg-6.8.0-139.sanitized.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166509/+attachment/5997817/+files/lp2166509-mt7922-dmesg-6.8.0-139.sanitized.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166509 Title: NULL pointer dereference in btmtk_usb_hci_wmt_sync kills MT7925 Bluetooth in 6.8.0-139 (regression from 6.8.0-138) Status in linux package in Ubuntu: Confirmed Bug description: The following report is filled by AI upon my request. However, I had the issue, I read about the fix that AI proposed, I applied it and the fix worked. So I can say that it was not a hallucination, at least for my computer. Would it work on others computers? Is it a good patch? I have no idea... [Impact] MediaTek MT7925/MT7921 USB Bluetooth controllers are completely non-functional on linux-image-6.8.0-139-generic. The controller oopses during firmware setup, the hci0 kworker exits with irqs disabled, and the adapter is left DOWN INIT with BD_ADDR 00:00:00:00:00:00. bluetoothctl reports no controller at all, so the machine has no usable Bluetooth: no pairing, and every previously paired device stops working. This is a regression introduced by 6.8.0-139.139. 6.8.0-138.138 is unaffected on identical hardware. MediaTek MT7925/MT7921 is the Bluetooth companion of the mt7921e Wi-Fi chip and is very common on recent AMD desktop boards and laptops, so the affected population is not small. [Fix] Two consecutive upstream commits from the same July 2024 MediaTek series, both first released in v6.11: d019930b0049 ("Bluetooth: btmtk: move btusb_mtk_hci_wmt_sync to btmtk.c") Moves the WMT handshake into btmtk.c. struct btusb_data is out of scope there, so the moved code reads the USB interface, device and control anchor out of the btmtk private area of hci_dev instead: struct btmtk_data *data = hci_get_priv(hdev); ... err = usb_autopm_get_interface(data->intf); 5c5e8c52e3ca ("Bluetooth: btmtk: move btusb_mtk_[setup, shutdown] to btmtk.c") Rewrites btusb_mtk_setup() to populate exactly those three fields before delegating to btmtk_usb_setup(). noble applied the first in 6.8.0-139.139, via LP: #2160250 ("Noble update: upstream stable patchset 2026-07-09"), but not the second. The consumer landed without its producer. btusb_mtk_setup() in noble therefore still has its pre-6.11 shape and sets only ->dev_id and ->reset_sync, leaving ->intf, ->udev and ->ctrl_anchor NULL. btmtk_usb_hci_wmt_sync() then calls usb_autopm_get_interface(NULL). Upstream is not affected: v6.11 and later carry both commits, v6.10 and earlier carry neither. Only a tree holding one without the other is broken. Backporting 5c5e8c52e3ca in full is not appropriate here: it moves btusb_mtk_setup()/btusb_mtk_shutdown() wholesale into btmtk.c and depends on the rest of the 6.11 MediaTek restructuring (btmtk_usb_setup(), btmtk_usb_shutdown(), the ISO data transmission series). The attached patch instead seeds the three fields the moved WMT code requires, which is what 5c5e8c52e3ca does for them upstream: mediatek = hci_get_priv(hdev); mediatek->dev_id = dev_id; mediatek->reset_sync = btusb_mtk_reset; + mediatek->intf = data->intf; + mediatek->udev = data->udev; + mediatek->ctrl_anchor = &data->ctrl_anchor; [Test Case] On an MT7925 USB adapter (0e8d:0616) running 6.8.0-139-generic, no Bluetooth adapter is usable: hci0 never leaves DOWN INIT, it carries no BD address, and bluetoothctl lists no controller. The kernel log shows why, at boot: BUG: kernel NULL pointer dereference, address: 0000000000000219 #PF: supervisor read access in kernel mode Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 6 PID: 225 Comm: kworker/u51:0 Tainted: P OE 6.8.0-139-generic #139-Ubuntu Workqueue: hci0 hci_power_on [bluetooth] RIP: 0010:__pm_runtime_resume+0x1b/0x80 Call Trace: usb_autopm_get_interface+0x1d/0x60 btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] btusb_mtk_setup+0x453/0x610 [btusb] hci_dev_setup_sync+0x6c/0x430 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0xb1/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] process_one_work+0x181/0x3a0 worker_thread+0x18b/0x330 kthread+0xef/0x120 note: kworker/u51:0[225] exited with irqs disabled Booting 6.8.0-138-generic on the same machine: no oops, Bluetooth works. With btusb.ko rebuilt from 6.8.0-139 sources plus the attached patch, the same machine boots to: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20250523103438 Bluetooth: hci0: Device setup in 159295 usecs Bluetooth: hci0: AOSP extensions version v1.00 $ hciconfig -a | head -3 hci0: Type: Primary Bus: USB BD Address: A8:3B:76:XX:XX:XX ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN and audio devices pair and stream normally. [Regression Potential] Very low. Three assignments of already-available values, confined to the MediaTek USB setup path, restoring parity with upstream btusb_mtk_setup(). Non-MediaTek controllers never execute this code. Without the assignments the fields are NULL and every consumer of them oopses, so there is no existing behaviour to preserve. Any risk would be confined to MediaTek USB Bluetooth, which is currently 100% broken on this kernel. [Other Info] Broken: linux-image-6.8.0-139-generic 6.8.0-139.139 Last good: linux-image-6.8.0-138-generic 6.8.0-138.138 Release: Ubuntu 24.04.4 LTS (noble) Adapter: MediaTek MT7925, USB 0e8d:0616 (companion to mt7921e Wi-Fi) Board: Micro-Star MSI MAG X670E TOMAHAWK WIFI (MS-7E12), BIOS 1.80 02/06/2024 Any MT7921/MT7922/MT7925 USB controller going through btusb_mtk_setup() should reproduce this identically. Patch, build scripts and full kernel logs for the broken, good and patched boots: https://github.com/LouisJULIEN/btusb-mtk-fix ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 17:08:27 2026 HibernationDevice: RESUME=none InstallationDate: Installed on 2024-03-20 (898 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Micro-Star International Co., Ltd. MS-7E12 ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_hve01w@/vmlinuz-6.8.0-139-generic root=ZFS=rpool/ROOT/ubuntu_hve01w ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-11-30 (643 days ago) dmi.bios.date: 02/06/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X670E TOMAHAWK WIFI (MS-7E12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd02/06/2024:br5.32:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX670ETOMAHAWKWIFI(MS-7E12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E12 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166509/+subscriptions
[Bug 2166509] Re: NULL pointer dereference in btmtk_usb_hci_wmt_sync kills MT7925 Bluetooth in 6.8.0-139 (regression from 6.8.0-138)
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/2166509 Title: NULL pointer dereference in btmtk_usb_hci_wmt_sync kills MT7925 Bluetooth in 6.8.0-139 (regression from 6.8.0-138) Status in linux package in Ubuntu: Confirmed Bug description: The following report is filled by AI upon my request. However, I had the issue, I read about the fix that AI proposed, I applied it and the fix worked. So I can say that it was not a hallucination, at least for my computer. Would it work on others computers? Is it a good patch? I have no idea... [Impact] MediaTek MT7925/MT7921 USB Bluetooth controllers are completely non-functional on linux-image-6.8.0-139-generic. The controller oopses during firmware setup, the hci0 kworker exits with irqs disabled, and the adapter is left DOWN INIT with BD_ADDR 00:00:00:00:00:00. bluetoothctl reports no controller at all, so the machine has no usable Bluetooth: no pairing, and every previously paired device stops working. This is a regression introduced by 6.8.0-139.139. 6.8.0-138.138 is unaffected on identical hardware. MediaTek MT7925/MT7921 is the Bluetooth companion of the mt7921e Wi-Fi chip and is very common on recent AMD desktop boards and laptops, so the affected population is not small. [Fix] Two consecutive upstream commits from the same July 2024 MediaTek series, both first released in v6.11: d019930b0049 ("Bluetooth: btmtk: move btusb_mtk_hci_wmt_sync to btmtk.c") Moves the WMT handshake into btmtk.c. struct btusb_data is out of scope there, so the moved code reads the USB interface, device and control anchor out of the btmtk private area of hci_dev instead: struct btmtk_data *data = hci_get_priv(hdev); ... err = usb_autopm_get_interface(data->intf); 5c5e8c52e3ca ("Bluetooth: btmtk: move btusb_mtk_[setup, shutdown] to btmtk.c") Rewrites btusb_mtk_setup() to populate exactly those three fields before delegating to btmtk_usb_setup(). noble applied the first in 6.8.0-139.139, via LP: #2160250 ("Noble update: upstream stable patchset 2026-07-09"), but not the second. The consumer landed without its producer. btusb_mtk_setup() in noble therefore still has its pre-6.11 shape and sets only ->dev_id and ->reset_sync, leaving ->intf, ->udev and ->ctrl_anchor NULL. btmtk_usb_hci_wmt_sync() then calls usb_autopm_get_interface(NULL). Upstream is not affected: v6.11 and later carry both commits, v6.10 and earlier carry neither. Only a tree holding one without the other is broken. Backporting 5c5e8c52e3ca in full is not appropriate here: it moves btusb_mtk_setup()/btusb_mtk_shutdown() wholesale into btmtk.c and depends on the rest of the 6.11 MediaTek restructuring (btmtk_usb_setup(), btmtk_usb_shutdown(), the ISO data transmission series). The attached patch instead seeds the three fields the moved WMT code requires, which is what 5c5e8c52e3ca does for them upstream: mediatek = hci_get_priv(hdev); mediatek->dev_id = dev_id; mediatek->reset_sync = btusb_mtk_reset; + mediatek->intf = data->intf; + mediatek->udev = data->udev; + mediatek->ctrl_anchor = &data->ctrl_anchor; [Test Case] On an MT7925 USB adapter (0e8d:0616) running 6.8.0-139-generic, no Bluetooth adapter is usable: hci0 never leaves DOWN INIT, it carries no BD address, and bluetoothctl lists no controller. The kernel log shows why, at boot: BUG: kernel NULL pointer dereference, address: 0000000000000219 #PF: supervisor read access in kernel mode Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 6 PID: 225 Comm: kworker/u51:0 Tainted: P OE 6.8.0-139-generic #139-Ubuntu Workqueue: hci0 hci_power_on [bluetooth] RIP: 0010:__pm_runtime_resume+0x1b/0x80 Call Trace: usb_autopm_get_interface+0x1d/0x60 btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] btusb_mtk_setup+0x453/0x610 [btusb] hci_dev_setup_sync+0x6c/0x430 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0xb1/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] process_one_work+0x181/0x3a0 worker_thread+0x18b/0x330 kthread+0xef/0x120 note: kworker/u51:0[225] exited with irqs disabled Booting 6.8.0-138-generic on the same machine: no oops, Bluetooth works. With btusb.ko rebuilt from 6.8.0-139 sources plus the attached patch, the same machine boots to: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20250523103438 Bluetooth: hci0: Device setup in 159295 usecs Bluetooth: hci0: AOSP extensions version v1.00 $ hciconfig -a | head -3 hci0: Type: Primary Bus: USB BD Address: A8:3B:76:XX:XX:XX ACL MTU: 1021:6 SCO MTU: 240:8 UP RUNNING PSCAN and audio devices pair and stream normally. [Regression Potential] Very low. Three assignments of already-available values, confined to the MediaTek USB setup path, restoring parity with upstream btusb_mtk_setup(). Non-MediaTek controllers never execute this code. Without the assignments the fields are NULL and every consumer of them oopses, so there is no existing behaviour to preserve. Any risk would be confined to MediaTek USB Bluetooth, which is currently 100% broken on this kernel. [Other Info] Broken: linux-image-6.8.0-139-generic 6.8.0-139.139 Last good: linux-image-6.8.0-138-generic 6.8.0-138.138 Release: Ubuntu 24.04.4 LTS (noble) Adapter: MediaTek MT7925, USB 0e8d:0616 (companion to mt7921e Wi-Fi) Board: Micro-Star MSI MAG X670E TOMAHAWK WIFI (MS-7E12), BIOS 1.80 02/06/2024 Any MT7921/MT7922/MT7925 USB controller going through btusb_mtk_setup() should reproduce this identically. Patch, build scripts and full kernel logs for the broken, good and patched boots: https://github.com/LouisJULIEN/btusb-mtk-fix ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 17:08:27 2026 HibernationDevice: RESUME=none InstallationDate: Installed on 2024-03-20 (898 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: Micro-Star International Co., Ltd. MS-7E12 ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_hve01w@/vmlinuz-6.8.0-139-generic root=ZFS=rpool/ROOT/ubuntu_hve01w ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-11-30 (643 days ago) dmi.bios.date: 02/06/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X670E TOMAHAWK WIFI (MS-7E12) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd02/06/2024:br5.32:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E12:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX670ETOMAHAWKWIFI(MS-7E12):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E12 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166509/+subscriptions
[Bug 2166579] Re: System hangs on shutdown/restart via KDE Start Menu on ASUS ROG Crosshair VIII Hero (X570)
** 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/2166579 Title: System hangs on shutdown/restart via KDE Start Menu on ASUS ROG Crosshair VIII Hero (X570) Status in linux package in Ubuntu: New Bug description: When attempting to shut down or restart the system using the KDE Plasma Start Menu / Session Manager on an ASUS ROG Crosshair VIII Hero (AMD X570) motherboard, the graphical session exits, but the system hangs indefinitely on a black screen with case fans and LEDs still powered on. Description: Ubuntu 26.04.1 LTS Release: 26.04 linux-image-generic: Installed: 7.0.0-31.31 Candidate: 7.0.0-31.31 Version table: *** 7.0.0-31.31 500 500 http://archive.ubuntu.com/ubuntu resolute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu resolute-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.0-14.14 500 500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages timothy@littlebullet:~$ Key Observations & Diagnostics: Direct Commands Work: Issuing direct kernel power commands (e.g., via custom desktop shortcuts or systemctl poweroff -i) powers down and restarts the motherboard and PSU cleanly every time, ruling out a physical motherboard ACPI or hardware power failure. Session Tear-Down Deadlock: The hang only occurs during the graphical session cleanup phase when initiated via the KDE Plasma UI, likely caused by an ACPI power-state transition deadlock or a driver failing to unhook during standard systemd user session shutdown. Hardware Context: Motherboard: ASUS ROG Crosshair VIII Hero (AMD X570) OS: Kubuntu (KDE Plasma) System configuration includes newly mounted local ext4 data drives under /mnt. New PSU has been installed Expected Behavior: Selecting "Shut Down" or "Restart" from the KDE Start Menu should cleanly terminate background processes, unmount filesystems, and pass power-off control to the Linux kernel/systemd without hanging. 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 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Sep 5 18:27:36 2026 InstallationDate: Installed on 2026-08-31 (5 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=a6c2c797-ae1a-43cf-9e4c-b5e66c81bbfd ro quiet splash reboot=pci amdgpu.runpm=0 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: 08/18/2026 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5601 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5601:bd08/18/2026:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166579/+subscriptions
[Bug 2161388] Re: radeon kernel module fails with "Invalid command stream"
** Attachment removed: "dmesg_7.0.0-31.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161388/+attachment/5997609/+files/dmesg_7.0.0-31.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161388 Title: radeon kernel module fails with "Invalid command stream" Status in linux package in Ubuntu: New Bug description: After the upgrade from 25.10 to 26.04, all recent kernel version have had this new failure in the dmesg output: radeon 0000:02:00.0: evergreen_cs_track_validate_cb:480 cb[0] bo too small (layer size 8847360, offset 0, max layer 1, bo size 4096, slice 34559) radeon 0000:02:00.0: evergreen_cs_track_validate_cb:485 problematic surf: (1920 1152) (4 4 1 1 2 1024 2) radeon 0000:02:00.0: evergreen_packet3_check:1950 invalid cmd stream 662 [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! My kernel parameters include radeon.dpm=1 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ad 1756 F.... wireplumber /dev/snd/controlC1: ad 1756 F.... wireplumber /dev/snd/controlC2: ad 1756 F.... wireplumber /dev/snd/seq: ad 1752 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Jul 20 23:02:45 2026 InstallationDate: Installed on 2025-07-25 (360 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=d0ba703d-8549-4bc4-b278-cf13189ad70a ro quiet radeon.dpm=1 acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-25 (26 days ago) dmi.bios.date: 12/22/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1202 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1202:bd12/22/2010:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:pfaToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161388/+subscriptions
[Bug 2166487] Re: Kernel oops (NULL pointer deref) in btmtk_usb_hci_wmt_sync on MediaTek MT7921 BT during hci_power_on, 6.8.0-139-generic
Confirmed on Ubuntu 24.04.4 LTS, Lenovo 82MS, with MediaTek MT7921 Wi- Fi/Bluetooth (Bluetooth USB ID 0489:e0cd). After upgrading to 6.8.0-139, every boot logs a NULL pointer dereference at address 0x219 in __pm_runtime_resume, called through usb_autopm_get_interface and btmtk_usb_hci_wmt_sync during hci_power_on. Closing the lid subsequently leaves the laptop unresponsive with a black screen, requiring a forced power-off. Booting the installed 6.8.0-138-generic kernel restores normal lid suspend and wake behavior. No other settings or packages were changed between these tests. This seems to be the same bug as reported for linux-hwe-6.8 package: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2165873 The non-HWE linux should probably receive the same fix too. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166487 Title: Kernel oops (NULL pointer deref) in btmtk_usb_hci_wmt_sync on MediaTek MT7921 BT during hci_power_on, 6.8.0-139-generic Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth fails to initialize on 6.8.0-139-generic (Ubuntu 24.04.4 LTS) on a system with a MediaTek MT7921 combo Wi-Fi/BT card. Bluetooth worked fine on 6.8.0-138-generic and earlier kernels; this appears after upgrading to 6.8.0-139-generic. hci0 remains DOWN with BD Address 00:00:00:00:00:00 and "No default controller available" is reported by bluetoothctl. The bluetooth service itself starts fine, but the controller never comes up. dmesg shows a kernel oops triggered during hci_power_on, in the MediaTek BT firmware setup path: CR2: 0000000000000219 RIP: __pm_runtime_resume+0x1b/0x80 Call Trace: usb_autopm_get_interface+0x1d/0x60 btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] btmtk_setup_firmware_79xx+0x1ca/0x360 [btmtk] btusb_mtk_setup+0x453/0x610 [btusb] hci_dev_setup_sync+0x6f/0x430 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0xb1/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] This looks like a NULL pointer dereference on the USB interface pointer (data->intf) passed to usb_autopm_get_interface(), similar in nature to the class of MediaTek btmtk/btusb autopm issues fixed upstream (e.g. commit "Bluetooth: btmtk: Fix failed to send func ctrl for MediaTek devices", and LP: #2092473 for linux-oem-6.11). Hardware: 01:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter DeviceName: Tequini MediaTek Wi-Fi 6 MT7921 + BT5.2 Kernel driver in use: mt7921e Steps to reproduce: 1. Boot 6.8.0-139-generic 2. Bluetooth service starts automatically (bluetoothd active) 3. hci0 never comes up; kernel oops appears in dmesg during hci_power_on 4. bluetoothctl show reports "No default controller available" Workaround: booting 6.8.0-138-generic (previous kernel) restores working Bluetooth on the same hardware. uname -a: Linux ict-hp 6.8.0-139-generic #139-Ubuntu SMP PREEMPT_DYNAMIC Sat Aug 1 03:52:05 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a: Distributor ID: Ubuntu Description: Ubuntu 24.04.4 LTS Release: 24.04 Codename: noble Full dmesg oops trace attached separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166487/+subscriptions
пятница
[Bug 2166226] Re: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30
Hello Marc, thanks for submitting a bug report. May I ask if this is a new regression? Did it work before, but start misbehaving after a kernel update? Has it ever worked? Thanks. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166226 Title: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu: 26.04.1 LTS Kernel: 7.0.0-30-generic, package 7.0.0-30.30 GPU: AMD Navi 23 / RX 6600 [1002:73ff], subsystem [1849:5217] Mesa: 26.0.8-1ubuntu0.3 linux-firmware: 20260319.git217ca6e4.1ubuntu The desktop first began stuttering and later stopped responding. At 16:41:37, amdgpu began reporting "Fence fallback timer expired". SysRq/NMI stack dumps repeatedly caught CPU 7 in amdgpu_device_rreg() from the display/vblank IRQ handler, while other CPUs were waiting in smp_call_function_many_cond(). AMDGPU later reported: ring sdma1 timeout, signaled seq=72398, emitted seq=72398 Starting sdma1 ring reset The reset did not complete. Repeated stack dumps for over three minutes showed the amdgpu-reset-dev worker in: amdgpu_device_rreg sdma_v5_2_stop_queue amdgpu_sdma_reset_engine sdma_v5_2_reset_queue amdgpu_job_timedout drm_sched_job_timedout Four seconds before the first amdgpu warning, an ASMedia ASM4242 USB4 bridge at 17:00.0 reported that it could not transition from D3cold to D0. This is on a different PCIe root port, so its relationship is unknown. The kernel is tainted P/O because this is a ZFS-root system using the ZFS DKMS module. The amdgpu module itself is the stock Ubuntu kernel module. Frequency: Happens pretty reliably within 24 hours of boot Recovery required: Requires hard reset USB4 activity at the time: None ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 2 17:11:37 2026 IwDevWlp16s0Link: Not connected. MachineType: Micro-Star International Co., Ltd. MS-7E70 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5ck8oa@/vmlinuz-7.0.0-30-generic root=ZFS=rpool/ROOT/ubuntu_5ck8oa ro init_on_alloc=0 nmi_watchdog=1 softlockup_panic=1 hardlockup_panic=1 crashkernel=1G crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-05 (59 days ago) dmi.bios.date: 09/24/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.A31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: PRO X870E-P WIFI (MS-7E70) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.A31:bd09/24/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E70:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX870E-PWIFI(MS-7E70):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E70 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166226/+subscriptions
[Bug 2166167] Re: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint
Hello Gerard, thanks for submitting a bug report. May I ask if this is a new regression? Did the display work before, but started misbehaving after a kernel update? Has it ever worked? Additionally, there is a new kernel available. Could you try running updates to see if the issue persists? Thanks! ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166167 Title: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint Status in linux package in Ubuntu: Incomplete Bug description: After resuming from suspend, USB-C DisplayPort Alt Mode stops working. The external monitor briefly wakes up on cable plug/unplug but reports "no signal". All DP connectors show "disconnected" in /sys/class/drm/. The following warning repeats in dmesg on each cable plug: WARNING: drivers/usb/typec/class.c:311 typec_altmode_update_active+0x101/0x110 [typec] ucsi_altmode_update_active+0x116/0x1b0 [typec_ucsi] ucsi_check_altmodes+0x92/0xd0 [typec_ucsi] Hardware: Thinkpad with AMD HawkPoint (Ryzen AI / 8000 series) Kernel: 7.0.0-30-generic (Ubuntu 26.04) Connector: USB-C to DisplayPort cable Workaround: none found (module reload crashes the system) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Sep 2 11:39:23 2026 InstallationDate: Installed on 2025-07-01 (428 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: LENOVO 21ME000RFR ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (85 days ago) dmi.bios.date: 05/21/2026 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: R2LET41W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 21ME000RFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR2LET41W(1.22):bd05/21/2026:br1.22:efr1.13:svnLENOVO:pn21ME000RFR:pvrThinkPadP14sGen5AMD:rvnLENOVO:rn21ME000RFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21ME_BU_Think_FM_ThinkPadP14sGen5AMD:pfaThinkPadP14sGen5AMD: dmi.product.family: ThinkPad P14s Gen 5 AMD dmi.product.name: 21ME000RFR dmi.product.sku: LENOVO_MT_21ME_BU_Think_FM_ThinkPad P14s Gen 5 AMD dmi.product.version: ThinkPad P14s Gen 5 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166167/+subscriptions
[Bug 2166520] Re: Dell XPS 13 9340: intel_backlight values change but Sharp C71M1 panel brightness does not
Probably a duplicate of bug 2161309 Please try kernel 7.0.0-31, which should be available on your repo mirror soon if it is not already. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166520 Title: Dell XPS 13 9340: intel_backlight values change but Sharp C71M1 panel brightness does not Status in linux package in Ubuntu: Incomplete Bug description: Hardware: * Dell XPS 13 9340 * BIOS/firmware version: 1.24.0 * GPU: Intel Meteor Lake-P [Intel Arc Graphics], PCI ID 8086:7d55 * Kernel driver: i915 * Internal display: Sharp SHP 5519, Dell C71M1, 2560×1600 QHD+ LED-backlit LCD * 64 GiB RAM Software: * Ubuntu 26.04.1 LTS, 64-bit * GNOME 50 * Wayland * Kernel 7.0.0-30-generic Expected behaviour: Changing brightness with the keyboard brightness keys or GNOME brightness slider should change the physical brightness of the internal display. Actual behaviour: The brightness OSD appears and its slider changes, but the physical brightness of the display remains completely unchanged. Additional tests: 1. /sys/class/backlight/intel_backlight exists. 2. The interface reports max_brightness=1023 and type=raw. 3. Writing a value directly to /sys/class/backlight/intel_backlight/brightness changes both brightness and actual_brightness, but the physical display brightness remains unchanged. 4. For example, after writing 300, both brightness and actual_brightness reported 300, while the display remained visually identical. 5. Brightness adjustment works correctly inside the Dell BIOS, so the panel and backlight hardware are functional. 6. The issue also occurs with kernel 7.0.0-29-generic. 7. The following i915 DPCD backlight modes were tested without success: * i915.enable_dpcd_backlight=1 * i915.enable_dpcd_backlight=2 * i915.enable_dpcd_backlight=3 8. The original boot configuration has been restored to i915.enable_dpcd_backlight=1. The issue therefore appears to be in the i915 backlight control for this specific Sharp/Dell panel: the sysfs values change, but the corresponding hardware brightness command is not applied. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: armando 6199 F.... pipewire armando 6209 F.... wireplumber /dev/snd/seq: armando 6199 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 18:43:49 2026 InstallationDate: Installed on 2026-06-05 (91 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 13 9340 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash xe.force_probe=7d14 i915.force_probe=!7d14 xe.fastboot=1 i915.enable_dpcd_backlight=1 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: 01/27/2026 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 08214J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd01/27/2026:br1.24:efr1.21:svnDellInc.:pnXPS139340:pvr:rvnDellInc.:rn08214J:rvrA00:cvnDellInc.:ct10:cvr:sku0C87:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 13 9340 dmi.product.sku: 0C87 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166520/+subscriptions
[Bug 2166119] Re: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71
Hey Leonardo, Thanks for submitting a bug report, and I'm glad to hear you were able to find a workaround. Has the USB bus been functioning normally since you did the Cold boot? For now I will mark this bug as Invalid, but if you find that the issue persists, please feel free to reopen it by setting the bug to "New" or "Confirmed". Thanks! ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166119 Title: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71 Status in linux package in Ubuntu: Invalid Bug description: Bluetooth worked normally on Ubuntu 24.04 LTS on this same laptop and hardware. After upgrading to Ubuntu 26.04 LTS, Bluetooth is no longer detected or available. Hardware: * ASUS VivoBook X512FB * Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter * PCI ID: 168c:0042 * Subsystem: Lite-On Communications Inc. 11ad:0836 * BIOS: X512FB.304 (08/26/2019) The Wi-Fi functionality of the QCA9377 continues to work normally. The Bluetooth controller is not detected: * `bluetoothctl list` returns no controller. * `lsusb` does not show a Bluetooth device. * No HCI device is present under `/sys/class/bluetooth`. * `rfkill` shows Bluetooth as unblocked. * `btusb` can be loaded successfully with `modprobe`, but no Bluetooth controller appears. The kernel log shows repeated USB enumeration failures on internal USB port 1-10: `usb 1-10: device descriptor read/64, error -110` followed by: `xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command` `usb 1-10: Device not responding to setup address.` `usb 1-10: device not accepting address 6, error -71` and finally: `usb usb1-port10: unable to enumerate USB device` The Bluetooth core and `btusb` driver are loaded, but no HCI controller is created because the underlying USB device fails to enumerate. The same laptop and QCA9377 hardware worked normally under Ubuntu 24.04 LTS. The Bluetooth problem appeared after upgrading to Ubuntu 26.04 LTS. This may be a kernel/USB/driver regression, as the same hardware worked normally on Ubuntu 24.04 LTS. However, I cannot confirm whether the issue is specifically a kernel regression yet. Expected behavior: The internal QCA9377 Bluetooth controller should be detected and available through `bluetoothctl`. Actual behavior: The Bluetooth controller fails USB enumeration with errors -110 and -71, no HCI controller is created, and Bluetooth is unavailable. Wi-Fi continues to work normally on the same QCA9377 adapter. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonardo 3444 F.... wireplumber /dev/snd/seq: leonardo 3433 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 19:26:53 2026 InstallationDate: Installed on 2026-08-28 (4 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:56d3 IMC Networks USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 006: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 006: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FB_X512FB ProcEnviron: LANG=pt_BR.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-30-generic root=UUID=810b2ac5-8f88-4cc7-9814-dc3780fab91a 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/26/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512FB.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512FB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512FB.304:bd08/26/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FB_X512FB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBook: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512FB_X512FB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166119/+subscriptions
[Bug 2165962] Re: Apple Trackpad not usable in Ubunty Desktop but works on laptop
Hey Salvador, thanks for submitting a bug report. Can you please verify the kernel version on your laptop? In a terminal window, type "uname -a" and paste the result. I am curious if the laptop (where the device works) is running a different version than the desktop. Also, did the trackpad work previously on the desktop? Or has it never worked? Thanks for your help. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165962 Title: Apple Trackpad not usable in Ubunty Desktop but works on laptop Status in linux package in Ubuntu: Incomplete Bug description: * Both Desktop and laptop have the same version of Ubuntu: 'Ubuntu 26.04.1 LTS' * Both show similar info when using lsusb: chava@desktop:~$ lsusb | grep -i apple Bus 005 Device 006: ID 05ac:0265 Apple, Inc. - When connecting to the desktop the USB trackpad does not work at all. - When connecting to the laptop the USB trackpad works like a charm. Multitouch, gestures, and all. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 21:39:58 2026 InstallationDate: Installed on 2026-09-01 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI 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:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165962/+subscriptions
[Bug 2166071] Re: Regression in 6.8.0-138-generic: Docker embedded DNS 127.0.0.11 times out, works with 6.8.0-137-generic
Thanks for submitting the bug report, and I'm glad the kernel update seems to have restored behavior back too normal. For now we can leave the bug as Invalid, but if others encounter a similar issue in the future, they can reference this bug or perhaps open a new report. Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166071 Title: Regression in 6.8.0-138-generic: Docker embedded DNS 127.0.0.11 times out, works with 6.8.0-137-generic Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 24.04.4 LTS There appears to be a kernel networking/DNS regression between 6.8.0-137-generic and 6.8.0-138-generic affecting Docker containers. After upgrading and booting kernel 6.8.0-138-generic, multiple unrelated Docker containers fail DNS resolution through Docker's embedded DNS resolver 127.0.0.11. Examples: CrowdSec: lookup version.crowdsec.net on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout NetBird: lookup pkgs.netbird.io on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout Watchtower: lookup index.docker.io on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout The problem appeared immediately after upgrading to and booting 6.8.0-138-generic. To verify the regression, I rebooted the same host using the previously installed kernel 6.8.0-137-generic. Without making any changes to Docker, the Docker networks, DNS configuration or the affected containers, DNS resolution immediately started working again. Affected kernel: 6.8.0-138-generic linux-image-6.8.0-138-generic 6.8.0-138.138 Working kernel: 6.8.0-137-generic linux-image-6.8.0-137-generic 6.8.0-137.137 Affected kernel uname: Linux dkr02 6.8.0-138-generic #138-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 31 22:41:49 UTC 2026 x86_64 GNU/Linux Steps to reproduce: 1. Boot the host with 6.8.0-138-generic. 2. Start the existing Docker containers. 3. DNS requests through Docker's embedded resolver 127.0.0.11 time out. 4. Reboot the identical host with 6.8.0-137-generic. 5. DNS resolution from the same Docker containers works again. Expected result: Docker container DNS resolution should continue to work after upgrading from kernel 6.8.0-137 to 6.8.0-138. Actual result: With 6.8.0-138, DNS requests from multiple Docker containers time out at Docker's 127.0.0.11 resolver. The issue is reproducible by changing only the booted kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166071/+subscriptions
четверг
Re: [Bug 2165927] Re: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic)
Hello Benjamin, Thank you for your response and for taking the time to look into the report. I understand that, since the issue was reproduced on Linux Mint, it cannot be investigated further through the Ubuntu kernel bug tracker. I will report it to the Linux Mint team as suggested. For completeness, I also tested the newly released kernel 7.0.0-31-generic on the same machine, with the same NVIDIA 595.84 driver and the same configuration. The hibernation/resume problem is now completely fixed. My regression testing is therefore: - 7.0.0-28-generic: hibernation/resume works correctly - 7.0.0-30-generic: resume fails with nv_pmops_freeze [nvidia] returns -5 - 7.0.0-31-generic: hibernation/resume works correctly again, with the complete desktop session restored This strongly suggests that the regression introduced in 7.0.0-30 was fixed in 7.0.0-31. Thank you again for your assistance and for pointing me toward the appropriate channel for the Linux Mint-specific report. Best regards, Seghir On Thu, 3 Sept 2026 at 19:25, Benjamin Wheeler <2165927@bugs.launchpad.net> wrote: > Hello, thanks for the information. Unfortunately, since you are using > Linux Mint, you will need to open a bug report with the Linux Mint team, > or reproduce the issue on Ubuntu (https://ubuntu.com/download). I > believe you can start here > https://forums.linuxmint.com/viewforum.php?f=49 > > Thank you and good luck! > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2165927 > > Title: > Hibernation resume fails with nv_pmops_freeze returns -5 on kernel > 7.0.0-30-generic (regression from 7.0.0-28-generic) > > Status in linux package in Ubuntu: > Invalid > > Bug description: > Ubuntu 26.04 LTS (Resolute Raccoon), kernel 7.0.0-30-generic (Ubuntu > 7.0.0-30.30-generic / upstream 7.0.12) — running as Linux Mint 22.3. > > System information: > - Distro: Linux Mint 22.3, based on Ubuntu 24.04 LTS (Noble Numbat), > kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30~24.04.1-generic). > - Host: ASUS TUF Dash F15 FX517ZE (Optimus hybrid graphics) > - CPU: Intel 12th Gen i7-12650H > - GPU: NVIDIA GeForce RTX 3050 Ti Mobile + Intel Alder Lake-P UHD > Graphics > - NVIDIA driver: 595.84 (Open Kernel Module) > - PRIME mode: on-demand > - Affected kernel: 7.0.0-30-generic (working: 7.0.0-28-generic, same > driver) > > Description: > > Hibernation worked reliably until approximately three weeks ago. After > a kernel upgrade from 7.0.0-28-generic to 7.0.0-30-generic, > hibernation resume consistently fails. > > The hibernation image is written successfully. On the next boot, the > kernel correctly detects and loads the saved image (100% progress, > "Image successfully loaded"), but immediately afterward the NVIDIA > driver fails to freeze the PCI device during the atomic restore step: > > nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] > returns -5 > nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5 > nvidia 0000:01:00.0: PM: failed to quiesce async: error -5 > PM: hibernation: Failed to load image, recovering. > PM: hibernation: resume failed (-5) > > The kernel then aborts the restore and boots fresh, discarding the > saved session entirely (all open applications are lost). > > Steps to reproduce: > 1. Open several applications (tested with ParaView, browser, terminal) > 2. sudo systemctl hibernate > 3. Power the machine back on > 4. Observe: fresh boot instead of restored session; dmesg shows the > error above > > Regression testing performed: > - Kernel 7.0.0-28-generic + driver 595.84 -> hibernation/resume works > perfectly, all windows restored > - Kernel 7.0.0-30-generic + driver 595.84 -> fails every time with the > error above > > Additional tests performed (none resolved the issue on kernel 30): > - NVreg_PreserveVideoMemoryAllocations=1 already set by default (via > /lib/modprobe.d/nvidia-runtimepm.conf) -- no effect > - Disabling GPU firmware (NVreg_EnableGpuFirmware=0) -- no effect, > identical error > - nvidia-hibernate.service, nvidia-resume.service, > nvidia-suspend.service all confirmed enabled > > Related bug (different symptom, same kernel/driver pair): > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164816 -- > describes a hibernation write/poweroff failure on the same kernel > 7.0.0-30-generic with a newer NVIDIA GPU (RTX 5060 Ti). My issue occurs > during resume/restore instead, which may indicate a broader PM regression > affecting the NVIDIA driver's PCI freeze/thaw callbacks introduced in this > kernel version. > > Full dmesg output attached showing the failure at the "nv_pmops_freeze" > line. > --- > ProblemType: Bug > ApportVersion: 2.28.3-0ubuntu0.1 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC2: seghir 1566 F.... wireplumber > /dev/snd/controlC0: seghir 1566 F.... wireplumber > /dev/snd/controlC1: seghir 1566 F.... wireplumber > /dev/snd/seq: seghir 1563 F.... pipewire > CRDA: N/A > CasperMD5CheckResult: unknown > CurrentDesktop: X-Cinnamon > DistroRelease: Linux Mint 22.3 > HibernationDevice: RESUME=UUID=3413547b-d881-4439-990b-994ec8807450 > MachineType: ASUSTeK COMPUTER INC. ASUS TUF Dash F15 FX517ZE_TUF517ZE > Package: linux (not installed) > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic > root=UUID=4b23724b-e789-4437-9b4e-ba97027762d7 ro quiet splash > resume=UUID=3413547b-d881-4439-990b-994ec8807450 > ProcVersionSignature: Ubuntu 7.0.0-30.30~24.04.1-generic 7.0.12 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: > linux-restricted-modules-7.0.0-30-generic N/A > linux-backports-modules-7.0.0-30-generic N/A > linux-firmware > 20240318.git3b128b60-0ubuntu2.29 > Tags: zena > Uname: Linux 7.0.0-30-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users > _MarkForUpload: True > dmi.bios.date: 12/15/2023 > dmi.bios.release: 5.26 > dmi.bios.vendor: American Megatrends International, LLC. > dmi.bios.version: FX517ZE.319 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: FX517ZE > 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: 3.10 > dmi.modalias: > dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX517ZE.319:bd12/15/2023:br5.26:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFDashF15FX517ZE_TUF517ZE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX517ZE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFDashF15: > dmi.product.family: ASUS TUF Dash F15 > dmi.product.name: ASUS TUF Dash F15 FX517ZE_TUF517ZE > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165927/+subscriptions > > -- Abdelghani SEGHIR *Research Laboratory of Applied Hydraulics and Environment (LRHAE), * *University of Bejaia, Algeria * blogue : a-seghir.blogspot.com/ tel : +213 667 98 47 08 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165927 Title: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic) Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 26.04 LTS (Resolute Raccoon), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30-generic / upstream 7.0.12) — running as Linux Mint 22.3. System information: - Distro: Linux Mint 22.3, based on Ubuntu 24.04 LTS (Noble Numbat), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30~24.04.1-generic). - Host: ASUS TUF Dash F15 FX517ZE (Optimus hybrid graphics) - CPU: Intel 12th Gen i7-12650H - GPU: NVIDIA GeForce RTX 3050 Ti Mobile + Intel Alder Lake-P UHD Graphics - NVIDIA driver: 595.84 (Open Kernel Module) - PRIME mode: on-demand - Affected kernel: 7.0.0-30-generic (working: 7.0.0-28-generic, same driver) Description: Hibernation worked reliably until approximately three weeks ago. After a kernel upgrade from 7.0.0-28-generic to 7.0.0-30-generic, hibernation resume consistently fails. The hibernation image is written successfully. On the next boot, the kernel correctly detects and loads the saved image (100% progress, "Image successfully loaded"), but immediately afterward the NVIDIA driver fails to freeze the PCI device during the atomic restore step: nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] returns -5 nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5 nvidia 0000:01:00.0: PM: failed to quiesce async: error -5 PM: hibernation: Failed to load image, recovering. PM: hibernation: resume failed (-5) The kernel then aborts the restore and boots fresh, discarding the saved session entirely (all open applications are lost). Steps to reproduce: 1. Open several applications (tested with ParaView, browser, terminal) 2. sudo systemctl hibernate 3. Power the machine back on 4. Observe: fresh boot instead of restored session; dmesg shows the error above Regression testing performed: - Kernel 7.0.0-28-generic + driver 595.84 -> hibernation/resume works perfectly, all windows restored - Kernel 7.0.0-30-generic + driver 595.84 -> fails every time with the error above Additional tests performed (none resolved the issue on kernel 30): - NVreg_PreserveVideoMemoryAllocations=1 already set by default (via /lib/modprobe.d/nvidia-runtimepm.conf) -- no effect - Disabling GPU firmware (NVreg_EnableGpuFirmware=0) -- no effect, identical error - nvidia-hibernate.service, nvidia-resume.service, nvidia-suspend.service all confirmed enabled Related bug (different symptom, same kernel/driver pair): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164816 -- describes a hibernation write/poweroff failure on the same kernel 7.0.0-30-generic with a newer NVIDIA GPU (RTX 5060 Ti). My issue occurs during resume/restore instead, which may indicate a broader PM regression affecting the NVIDIA driver's PCI freeze/thaw callbacks introduced in this kernel version. Full dmesg output attached showing the failure at the "nv_pmops_freeze" line. --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: seghir 1566 F.... wireplumber /dev/snd/controlC0: seghir 1566 F.... wireplumber /dev/snd/controlC1: seghir 1566 F.... wireplumber /dev/snd/seq: seghir 1563 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 HibernationDevice: RESUME=UUID=3413547b-d881-4439-990b-994ec8807450 MachineType: ASUSTeK COMPUTER INC. ASUS TUF Dash F15 FX517ZE_TUF517ZE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=4b23724b-e789-4437-9b4e-ba97027762d7 ro quiet splash resume=UUID=3413547b-d881-4439-990b-994ec8807450 ProcVersionSignature: Ubuntu 7.0.0-30.30~24.04.1-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-30-generic N/A linux-backports-modules-7.0.0-30-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 Tags: zena Uname: Linux 7.0.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/15/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX517ZE.319 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX517ZE 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: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX517ZE.319:bd12/15/2023:br5.26:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFDashF15FX517ZE_TUF517ZE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX517ZE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFDashF15: dmi.product.family: ASUS TUF Dash F15 dmi.product.name: ASUS TUF Dash F15 FX517ZE_TUF517ZE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165927/+subscriptions