Hi, Thanks for submitting a bug report. Does this happen every time or does it only happen occasionally? Was the occurrence on 2026-09-24 the first time this happened? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168830 Title: Intel Cannon Point-LP xHCI controller dies on resume from deep suspend on Lenovo ThinkPad L490 Status in linux package in Ubuntu: New Bug description: Kubuntu 26.04, kernel 7.0.0-34-generic (Ubuntu package 7.0.0-34.34) Machine: Lenovo ThinkPad L490, type 20Q5 BIOS: R0ZET60W (1.38) Controller: Intel Cannon Point-LP USB 3.1 xHCI [8086:9ded], PCI 0000:00:14.0 Sleep mode: deep (s2idle is also advertised) Lenovo USB-C dock attached (USB hubs 17ef:3072 and 17ef:3073). Repeated failure after suspend/resume, including automatic idle suspend. Latest occurrence: 2026-09-29, suspend 09:15:10 CEST, resume 09:27:10 CEST. Expected: USB devices reconnect and remain usable after resume. Actual: all USB devices disappear, including dock keyboard/mouse and internal Goodix fingerprint sensor. External monitor continues working. lsusb shows only USB2/USB3 root hubs. Internal keyboard and touchpad remain usable. Kernel messages: xhci_hcd 0000:00:14.0: xHCI host not responding to stop endpoint command xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead xhci_hcd 0000:00:14.0: HC died; cleaning up usb 1-4.4.4: PM: dpm_run_callback(): usb_dev_resume returns -22 usb 1-4.4.4: PM: failed to resume async: error -22 Followed by disconnection of all USB devices. Recovery: unbind and rebind PCI 0000:00:14.0 from xhci_hcd restores USB without reboot. The issue also occurred on 2026-09-24. A separate fingerprint daemon hang occurs following USB re-enumeration; restarting fprintd fixes that symptom. A local sleep service now stops fprintd before suspend and starts it after resume, but the whole-controller failure still occurs. No controlled comparison with older kernels or suspend without the dock has been performed, so a kernel regression is not yet established. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168830/+subscriptions
вторник
[Bug 2168825] Re: xruns in HDMI audio after kernel 7.0.0-27
Hi, Thanks for submitting a detailed bug report. You mentioned that 7.0.0-27 is fine and 7.0.0-29 isn't, can you confirm whether the issue appears in 7.0.0-28? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168825 Title: xruns in HDMI audio after kernel 7.0.0-27 Status in linux package in Ubuntu: New Bug description: forum thread: https://discourse.ubuntu.com/t/pipewire-crackling-on- kernels-later-than-7-0-0-27/88358 I output audio through HDMI to my receiver, via an AMD gpu (a 9070xt), via pipewire. Since upgrading kernels past 7.0.0-27, there are crackling noises and xruns during lots of different kinds of playback, and even when idle. The receiver makes a small popping noise when the audio stream is interrupted, which happens multiple times per second often times even when no audio is playing. Increasing pipewire’s quantum to very high numbers (like 64k, over half a second) does not seem to fix this. It also happens when the system is idle, not just under load; the only fix I’ve found is to keep booting with the 7.0.0-27 kernel. Playing completely silent audio from certain programs like audacity seems to help, but is not really a fix. I vaguely suspect this might be an issue with amdgpu but I really can’t tell and don’t know how best to debug it from here. This bug report bundle was taken with 7.0.0-34, but it has been happening since at least 7.0.0-29. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC3D0c: widders 6428 F...m pipewire /dev/snd/pcmC3D0p: widders 6428 F...m pipewire /dev/snd/pcmC0D9p: widders 6428 F...m pipewire /dev/snd/seq: widders 6428 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 23:40:46 2026 InstallationDate: Installed on 2018-11-14 (2876 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name 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-34-generic root=UUID=86127bef-7d71-4426-8373-82798d2c8063 ro rootflags=subvol=@ quiet splash intel_iommu=on snd-hda-intel.snoop=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-01 (90 days ago) dmi.bios.date: 12/14/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI 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.:bvr1807:bd12/14/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI: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 modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-06-29T02:14:01.068739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168825/+subscriptions
[Bug 2165873] Re: Bluetooth fails to initialize due to a kernel NULL pointer error
6.8.0-142-lowlatency is also affected -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165873 Title: Bluetooth fails to initialize due to a kernel NULL pointer error Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.8 package in Ubuntu: Confirmed Status in linux source package in Noble: In Progress Status in linux-hwe-6.8 source package in Noble: In Progress Bug description: SRU Justification [Impact] Bluetooth fails to start on HP systems with a MediaTek MT7922 controller (CID: 202401-33402) running 6.8.0-139.139~22.04.1. The kernel oopses during Bluetooth power-on. The worker thread dies, so hci0 stays in DOWN INIT and its BD address is all zeros. Bluetooth is unusable. rfkill unblock and hciconfig do not help. Error log: Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20231120183620 BUG: kernel NULL pointer dereference, address: 0000000000000219 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 9 PID: 340 Comm: kworker/u33:1 Not tainted 6.8.0-139-generic Workqueue: hci0 hci_power_on [bluetooth] RIP: 0010:__pm_runtime_resume+0x1b/0x80 Call Trace: <TASK> usb_autopm_get_interface+0x1d/0x60 btmtk_usb_hci_wmt_sync+0xb9/0x340 [btmtk] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] btusb_mtk_setup+0x2d6/0x610 [btusb] hci_dev_setup_sync+0x6c/0x440 [bluetooth] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] hci_dev_open_sync+0x8b/0x350 [bluetooth] hci_dev_do_open+0x28/0x70 [bluetooth] hci_power_on+0x50/0x210 [bluetooth] Hits 3 out of 3 boots. 6.8.0-138.138~22.04.1 is fine. This breaks these checkbox tests: com.canonical.certification::bluetooth/detect-output com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 This is not limited to the reporting machine. Any MediaTek MT766x or MT79xx USB Bluetooth controller takes the same path and hits the same oops on 6.8.0-139. [Fix] 6.8.0-139 picked up d019930b0049 ("Bluetooth: btmtk: move btusb_mtk_hci_wmt_sync to btmtk.c", v6.11) as a stable dependency of the urb->setup_packet leak fix. That commit moves the WMT command path into btmtk.c, where it reads intf, udev and ctrl_anchor out of struct btmtk_data. The commit that fills those three fields in is the next one in the same upstream series, and it was not picked: 5c5e8c52e3ca Bluetooth: btmtk: move btusb_mtk_[setup, shutdown] to btmtk.c (v6.11) So the pointers stay NULL. The first WMT command calls usb_autopm_get_interface(NULL) and oopses. The fix is to backport 5c5e8c52e3ca so the series is complete again. It adds the missing assignments in btusb_mtk_setup(): btmtk_data->drv_name = btusb_driver.name; btmtk_data->intf = data->intf; btmtk_data->udev = data->udev; btmtk_data->ctrl_anchor = &data->ctrl_anchor; btmtk_data->reset_sync = btusb_mtk_reset; udev and ctrl_anchor are just as NULL as intf, and are used by the WMT receive URB, so all of them are needed. A NULL check on intf alone would only move the oops. [Test Plan] On a machine with a MediaTek MT7922 Bluetooth controller. Boot the machine, then check for the oops: $ dmesg | grep -A20 'NULL pointer' $ journalctl -b -0 -k | grep btmtk Check the controller came up: $ sudo rfkill unblock bluetooth $ hciconfig -a $ hcitool dev Without patch: dmesg shows the NULL pointer oops in __pm_runtime_resume with btmtk_usb_hci_wmt_sync in the call trace. hciconfig shows hci0 DOWN INIT with BD Address 00:00:00:00:00:00. hcitool dev lists no device. With patch: no oops in dmesg. hciconfig shows hci0 UP RUNNING with a real BD address. hcitool dev lists hci0. Then run the two failing tests: $ checkbox-cli run com.canonical.certification::bluetooth/detect-output $ checkbox-cli run com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 Both pass with the patch, both fail without it. [Where problems could occur] Could break the btusb and btmtk drivers for all MediaTek Bluetooth controllers. This is not a small patch. It moves btusb_mtk_setup() and btusb_mtk_shutdown() and their helpers out of btusb.c into btmtk.c, so the whole MediaTek setup path is touched. If the move dropped or changed something, MediaTek Bluetooth would fail to set up. That would show up as "Failed to set up firmware" or "Failed to send wmt func ctrl" in dmesg, or as a timeout during hci0 power-on, and Bluetooth would stay down. The device reset path also moves (btusb_mtk_subsys_reset becomes btmtk_usb_subsys_reset). If that is wrong, chip recovery after a firmware crash would fail and the controller would need a reboot to come back. Nothing outside drivers/bluetooth is touched. Other Bluetooth vendors (Intel, Realtek, Qualcomm, Broadcom) are not affected, because btusb only calls this code for MediaTek devices. [Other Info] The patch is upstream in v6.11. It is the second half of a two-commit series; the first half is already in 6.8.0-139, which is what caused the regression. The backport needed manual conflict resolution in drivers/bluetooth/btusb.c. 6.8 is missing the intermediate commits that added fw_flavor handling and the BTMTK_FIRMWARE_LOADED flag, so the old copies of btusb_mtk_func_query(), btusb_mtk_uhw_reg_*(), btusb_mtk_reg_read(), btusb_mtk_id_get(), btusb_mtk_reset_done(), btusb_mtk_subsys_reset() and the open-coded btusb_mtk_setup() body all conflicted. Those are exactly the functions this commit deletes, so the upstream side was taken. The resulting btusb_mtk_setup() is identical to upstream at 5c5e8c52e3ca. =========================== The Bluetooth controller fails to initialize on kernel 6.8.0-139.139~22.04.1. During hci_power_on, the MediaTek btmtk driver hits a kernel NULL pointer dereference, the handling kworker dies with IRQs disabled, and hci0 is left stuck in DOWN INIT with an all-zero BD address. The previous kernel 6.8.0-138.138~22.04.1 is unaffected, with identical linux-firmware(20220329.git681281e4-0ubuntu3.42) and bluez(5.64-0ubuntu1.4), this seems to be a kernel regression. This failure affects the following checkbox tests: - com.canonical.certification::bluetooth/detect-output - com.canonical.certification::bluetooth4/beacon_eddystone_url_hc0 Machines: - https://certification.canonical.com/hardware/202401-33402/ Steps to reproduce: 1. Boot the machine with kernel 6.8.0-139.139~22.04.1. 2. Checkbox dmesg for crash, null pointer appears in btmtk_usb_hci_wmt_sync during hci power on. 3. run `sudo rfkill unblock bluetooth; hciconfig -a; hcitool dev` to check the controller state. 4. reboot into 6.8.0-138.138~22.04.1 and repeat steps 2-3. Fail rate: 3/3 on 6.8.0.139 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-139.139~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1307 F.... pulseaudio /dev/snd/controlC0: ubuntu 1307 F.... pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail Date: Mon Aug 31 13:19:26 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20240408-800 InstallationDate: Installed on 2026-08-28 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20240408-800 MachineType: HP HP ZBook Power 16 inch G11 A Mobile Workstation PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=6006e56e-4c1e-49e1-8a56-4c55eea6d70d ro automatic-oem-config 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-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.42 SourcePackage: linux-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W85 Ver. 01.01.01 dmi.board.name: 8C95 dmi.board.vendor: HP dmi.board.version: KBC Version 08.40.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 8.64 dmi.modalias: dmi:bvnHP:bvrW85Ver.01.01.01:bd03/21/2024:br1.1:efr8.64:svnHP:pnHPZBookPower16inchG11AMobileWorkstationPC:pvrSBKPF:rvnHP:rn8C95:rvrKBCVersion08.40.00:cvnHP:ct10:cvr:skuXW8SKU3#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 16 inch G11 A Mobile Workstation PC dmi.product.sku: XW8SKU3#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165873/+subscriptions
[Bug 2166569] Re: btmtk: NULL pointer dereference in usb_autopm_get_interface during btmtk_setup_firmware_79xx on 6.8.0-139-generic (MT7961)
*** This bug is a duplicate of bug 2165873 *** https://bugs.launchpad.net/bugs/2165873 ** Also affects: linux-lowlatency (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/2166569 Title: btmtk: NULL pointer dereference in usb_autopm_get_interface during btmtk_setup_firmware_79xx on 6.8.0-139-generic (MT7961) Status in linux package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-6.8.0-139-generic on Ubuntu 24.04 LTS, Bluetooth stopped working entirely. The btmtk driver hits a NULL pointer dereference while setting up the MT7961 controller firmware, which kills the hci_power_on kworker. As a result hci0 is registered (visible in rfkill) but never initialized, and bluetoothctl reports "No default controller available". Booting 6.8.0-138-generic makes Bluetooth work again, so this is a regression introduced in 6.8.0-139. Hardware: Acer Aspire A515-57 (Ganymede_ADU), BIOS V1.26 01/23/2024 Bluetooth device: USB 04ca:3802 Lite-On Wireless_Device (MediaTek MT7961, combo with mt7921e Wi-Fi) Wi-Fi side (mt7921e) loads fine on both kernels; only Bluetooth is affected. linux-firmware 20240318.git3b128b60.0ubuntu3.1, BT_RAM_CODE_MT7961_* present in /lib/firmware/mediatek/ Steps to reproduce: 1. Boot 6.8.0-139-generic 2. bluetoothctl show Expected: controller is listed. Actual: "No default controller available", and dmesg shows the Oops below. Kernel Oops from 6.8.0-139-generic: [ 3.400181] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240219111427 [ 3.400191] BUG: kernel NULL pointer dereference, address: 0000000000000219 [ 3.400195] #PF: supervisor read access in kernel mode [ 3.400196] #PF: error_code(0x0000) - not-present page [ 3.400201] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 3.400204] CPU: 6 PID: 139 Comm: kworker/u25:0 Not tainted 6.8.0-139-generic #139-Ubuntu [ 3.400206] Hardware name: Acer Aspire A515-57/Ganymede_ADU, BIOS V1.26 01/23/2024 [ 3.400208] Workqueue: hci0 hci_power_on [bluetooth] [ 3.400257] RIP: 0010:__pm_runtime_resume+0x1b/0x80 [ 3.400265] RSP: 0018:ffffcced006efb30 EFLAGS: 00010246 [ 3.400267] RAX: ffff89480b5254d0 RBX: 0000000000000050 RCX: 0000000000000000 [ 3.400268] RDX: 0000000000000035 RSI: 0000000000000000 RDI: 0000000000000050 [ 3.400276] CR2: 0000000000000219 CR3: 000000064a63c001 CR4: 0000000000f70ef0 [ 3.400279] Call Trace: [ 3.400281] <TASK> [ 3.400284] usb_autopm_get_interface+0x1d/0x60 [ 3.400290] btmtk_usb_hci_wmt_sync+0xa9/0x2e0 [btmtk] [ 3.400295] btmtk_setup_firmware_79xx+0x1c7/0x360 [btmtk] [ 3.400298] btusb_mtk_setup+0x453/0x610 [btusb] [ 3.400302] hci_dev_setup_sync+0x6c/0x430 [bluetooth] [ 3.400346] hci_dev_init_sync+0x3e/0x1c0 [bluetooth] [ 3.400381] hci_dev_open_sync+0xb1/0x350 [bluetooth] [ 3.400414] hci_dev_do_open+0x28/0x70 [bluetooth] [ 3.400440] hci_power_on+0x50/0x210 [bluetooth] [ 3.400470] process_one_work+0x181/0x3a0 [ 3.400474] worker_thread+0x18b/0x330 [ 3.400479] kthread+0xef/0x120 [ 3.400482] ret_from_fork+0x44/0x70 [ 3.400487] ret_from_fork_asm+0x1b/0x30 [ 3.400490] </TASK> Note: this report was filed while running 6.8.0-138-generic (the working kernel), so the automatically collected data reflects -138, not the affected -139. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-138-generic 6.8.0-138.138 ProcVersionSignature: Ubuntu 6.8.0-138.138-generic 6.8.12 Uname: Linux 6.8.0-138-generic x86_64 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: bruno 2629 F.... wireplumber /dev/snd/seq: bruno 2627 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 07:40:39 2026 MachineType: Acer Aspire A515-57 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-138-generic root=UUID=bddae004-6880-4401-99e0-54b9652f9570 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: Upgraded to noble on 2025-12-28 (250 days ago) dmi.bios.date: 01/23/2024 dmi.bios.release: 1.26 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ganymede_ADU dmi.board.vendor: ADL dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd01/23/2024:br1.26:efr1.26:svnAcer:pnAspireA515-57:pvrV1.26:rvnADL:rnGanymede_ADU:rvrV1.26:cvnAcer:ct10:cvrV1.26:sku0000000000000000: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-57 dmi.product.sku: 0000000000000000 dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166569/+subscriptions
[Bug 2168884] Re: ThinkPad X13 Gen 2 AMD (20XJ): ~11 second s2idle resume delay with AMD IOMMU enabled; delay disappears with amd_iommu=off
** 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/2168884 Title: ThinkPad X13 Gen 2 AMD (20XJ): ~11 second s2idle resume delay with AMD IOMMU enabled; delay disappears with amd_iommu=off Status in linux package in Ubuntu: New Bug description: I am seeing a reproducible ~11 second delay when resuming a Lenovo ThinkPad X13 Gen 2 AMD, machine type 20XJ, from s2idle. After opening the lid, the display remains black for approximately 11 seconds before the system resumes normally. The issue disappears completely when booting once with: amd_iommu=off With AMD IOMMU disabled, resume is effectively immediate. The closely related ThinkPad X13 Gen 2 AMD machine type 20XH is currently present in the AMD PMC firmware bug quirk table, while 20XJ is not. The existing quirk is documented as working around a platform firmware issue where an SMI handler during the NVMe D3→D0 transition can cause large resume delays while IOMMU translation is enabled. This appears consistent with the behavior observed on this 20XJ system. GitHub Hardware System: Lenovo ThinkPad X13 Gen 2 AMD Machine type: 20XJ CPU: AMD Ryzen 5 PRO 5650U with Radeon Graphics RAM: 16 GB NVMe: Samsung MZVLB512HBJQ-000L7 The system also contains a Quectel EM120R-GL LTE modem, but disabling Wireless WAN completely in UEFI had no effect on the resume delay. Firmware BIOS version: R1NET67W (1.37) BIOS date: 04/16/2026 Software Kernel: 7.0.0-34-generic linux-firmware: 20260319.git217ca6e4.1ubuntu Suspend mode: $ cat /sys/power/mem_sleep [s2idle] The firmware exposes only s2idle on this system. Steps to reproduce 1. Boot normally with AMD IOMMU enabled. 2. Log into the desktop. 3. Suspend the laptop normally by closing the lid or invoking suspend. 4. Wait for the system to enter s2idle. 5. Open the lid. 6. Measure the time before the display becomes active. Actual result The screen remains black for approximately: 11+ seconds before the system becomes usable. The problem is reproducible across repeated suspend/resume cycles. Expected result Resume should occur within approximately 1–2 seconds, as it does when AMD IOMMU is disabled. Important A/B test I edited the GRUB kernel command line for one boot only and appended: amd_iommu=off No other relevant configuration was changed. Result: Normal boot / IOMMU enabled: ~11 seconds black screen after opening lid amd_iommu=off: resume immediately / delay disappears This result is reproducible and strongly suggests that the delay depends on AMD IOMMU being enabled. WWAN test Because this system contains a Quectel EM120R-GL LTE modem using mhi_pci_generic, I also tested whether the WWAN device was responsible. Detected device: 04:00.0 Unassigned class [ff00]: Quectel Wireless Solutions Co., Ltd. EM120R-GL LTE Modem [1eac:1001] Kernel driver in use: mhi_pci_generic Kernel modules: mhi_pci_generic ModemManager detects: [Quectel] EM120R_GL I disabled Wireless WAN completely in ThinkPad UEFI: Security -> I/O Port Access -> Wireless WAN: Off The ~11 second resume delay remained unchanged. Therefore the WWAN modem does not appear to be responsible for this issue. Relevant kernel observations The system logs contain recurring AMD display firmware diagnostics: amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data However, once the visible kernel resume sequence begins, the AMD GPU itself resumes quickly: amdgpu 0000:05:00.0: SMU is resuming... amdgpu 0000:05:00.0: SMU is resumed successfully! and PM: suspend exit follows shortly afterwards. The logs also show: nvme nvme0: D3 entry latency set to 8 seconds I understand that this value is a power-management latency value and is not by itself evidence of an 8-second measured stall. The long user-visible delay appears to occur before the normal device resume sequence becomes visible in the kernel log, which would be consistent with a firmware/SMI-level delay. AMD PMC quirk observation Current upstream drivers/platform/x86/amd/pmc/pmc-quirks.c contains an entry for: X13 Gen2 AMD DMI_PRODUCT_NAME = "20XH" using: quirk_s2idle_spurious_8042 but I do not see a corresponding 20XJ entry. GitHub The same source describes the relevant workaround as applying to systems where a firmware SMI handler during the NVMe D3→D0 transition can cause large resume delays when IOMMU translation is enabled. GitHub My affected machine is: ThinkPad X13 Gen 2 AMD DMI product name: 20XJ This makes me suspect that 20XJ may require the same quirk currently applied to 20XH. Additional observation Searching the boot log for: Using s2idle quirk produces no output on this machine. For example: sudo journalctl -b -k | grep -i "Using s2idle quirk" returns nothing. The AMD PMC driver prints such a message when an applicable s2idle_bug_mmio quirk is selected. GitHub Proposed investigation Could you please confirm whether ThinkPad X13 Gen 2 AMD machine type 20XJ should use the same AMD PMC firmware workaround as 20XH? A likely DMI addition would conceptually correspond to the existing X13 Gen 2 AMD entry, but match: DMI_PRODUCT_NAME, "20XJ" I have not applied a custom kernel patch yet, so I have not independently verified the quirk itself on 20XJ. What I have verified is: 20XJ + normal IOMMU configuration -> ~11 s resume delay 20XJ + WWAN disabled -> ~11 s resume delay 20XJ + amd_iommu=off -> immediate resume ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 20:08:18 2026 InstallationDate: Installed on 2026-09-23 (6 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: LENOVO 20XJS1XM00 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=/vmlinuz-7.0.0-34-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: 04/16/2026 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R1NET67W (1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20XJS1XM00 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnLENOVO:bvrR1NET67W(1.37):bd04/16/2026:br1.37:efr1.37:svnLENOVO:pn20XJS1XM00:pvrThinkPadX13Gen2a:rvnLENOVO:rn20XJS1XM00:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XJ_BU_Think_FM_ThinkPadX13Gen2a:pfaThinkPadX13Gen2a: dmi.product.family: ThinkPad X13 Gen 2a dmi.product.name: 20XJS1XM00 dmi.product.sku: LENOVO_MT_20XJ_BU_Think_FM_ThinkPad X13 Gen 2a dmi.product.version: ThinkPad X13 Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168884/+subscriptions
Re: [Bug 2168362]
El 23/9/26 a las 23:46, Daniel Letzeisen escribió: > The error is caused by a file/script from VMWare. I suggest contacting > VMWare, searching their forums, etc. > > -------------------------------------------- > > Configurando linux-headers-7.0.0-34-generic (7.0.0-34.34~24.04.1) ... > /etc/kernel/header_postinst.d/99-sign-vmware: > run-parts: failed to exec /etc/kernel/header_postinst.d/99-sign-vmware: Exec format error > run-parts: /etc/kernel/header_postinst.d/99-sign-vmware exited with return code 1 > > ** Changed in: linux (Ubuntu) > Status: New => Invalid Gracias por su amabilidad. Thank you for your kindness. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168362 Title: package linux-headers-generic 6.8.0-142.142 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in linux package in Ubuntu: Invalid Bug description: El paquete falla al instalarse en una actualización rutinaria. Ninguna razón valida que se pueda presuponer. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-generic 6.8.0-142.142 ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Wed Sep 23 23:25:16 2026 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2025-01-18 (613 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: ASUS System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=da9075b1-8f68-4a9d-aa10-d4ed20a8170c 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. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2.1 PythonDetails: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1 RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-generic 6.8.0-142.142 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2026 dmi.bios.release: 16.81 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1681 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X870-PLUS WIFI 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.:bvr1681:bd06/18/2026:br16.81:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX870-PLUSWIFI: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/2168362/+subscriptions
понедельник
[Bug 2160082] Re: Linux, Ubuntu, 24.04, System hangs for about 10 seconds when unplug external monitor cable on non TBT dock
1. plug non-TBT dock with external display and check internal/external displays both work, make sure touch touch also works 2. unplug non-TBT and keep typing on touch, make sure touch is working. 3. Repeat steps 1,2 for 10 times and no hang found. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160082 Title: Linux, Ubuntu, 24.04, System hangs for about 10 seconds when unplug external monitor cable on non TBT dock Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Summary] System hangs for about 10 seconds when unplug external monitor cable on non TBT dock or connected external monitor cable into non TBT dock and then unplug dock cable. [Steps to reproduce] Plug the external monitor into non TBT dock. Plug non TBT dock into the system. Unplug non TBT cable or the external monitor cable. Found the system hangs for about 10 seconds. [Expected result] The system should work without any lagging or hanging when unplugging the monitor or the dock cable. [Actual result] The system hangs/freezes for about 10 seconds whenever the external monitor cable or the non-TBT dock cable is unplugged. [Failure rate] 100% [Affected test cases] 171316 Ubuntu24.04_OS - OOBE Test [Additional information] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2160082/+subscriptions
[Bug 2168825] [NEW] xruns in HDMI audio after kernel 7.0.0-27
Public bug reported: forum thread: https://discourse.ubuntu.com/t/pipewire-crackling-on- kernels-later-than-7-0-0-27/88358 I output audio through HDMI to my receiver, via an AMD gpu (a 9070xt), via pipewire. Since upgrading kernels past 7.0.0-27, there are crackling noises and xruns during lots of different kinds of playback, and even when idle. The receiver makes a small popping noise when the audio stream is interrupted, which happens multiple times per second often times even when no audio is playing. Increasing pipewire’s quantum to very high numbers (like 64k, over half a second) does not seem to fix this. It also happens when the system is idle, not just under load; the only fix I’ve found is to keep booting with the 7.0.0-27 kernel. Playing completely silent audio from certain programs like audacity seems to help, but is not really a fix. I vaguely suspect this might be an issue with amdgpu but I really can’t tell and don’t know how best to debug it from here. This bug report bundle was taken with 7.0.0-34, but it has been happening since at least 7.0.0-29. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC3D0c: widders 6428 F...m pipewire /dev/snd/pcmC3D0p: widders 6428 F...m pipewire /dev/snd/pcmC0D9p: widders 6428 F...m pipewire /dev/snd/seq: widders 6428 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 23:40:46 2026 InstallationDate: Installed on 2018-11-14 (2876 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name 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-34-generic root=UUID=86127bef-7d71-4426-8373-82798d2c8063 ro rootflags=subvol=@ quiet splash intel_iommu=on snd-hda-intel.snoop=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-01 (90 days ago) dmi.bios.date: 12/14/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI 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.:bvr1807:bd12/14/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI: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 modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-06-29T02:14:01.068739 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2168825 Title: xruns in HDMI audio after kernel 7.0.0-27 Status in linux package in Ubuntu: New Bug description: forum thread: https://discourse.ubuntu.com/t/pipewire-crackling-on- kernels-later-than-7-0-0-27/88358 I output audio through HDMI to my receiver, via an AMD gpu (a 9070xt), via pipewire. Since upgrading kernels past 7.0.0-27, there are crackling noises and xruns during lots of different kinds of playback, and even when idle. The receiver makes a small popping noise when the audio stream is interrupted, which happens multiple times per second often times even when no audio is playing. Increasing pipewire’s quantum to very high numbers (like 64k, over half a second) does not seem to fix this. It also happens when the system is idle, not just under load; the only fix I’ve found is to keep booting with the 7.0.0-27 kernel. Playing completely silent audio from certain programs like audacity seems to help, but is not really a fix. I vaguely suspect this might be an issue with amdgpu but I really can’t tell and don’t know how best to debug it from here. This bug report bundle was taken with 7.0.0-34, but it has been happening since at least 7.0.0-29. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC3D0c: widders 6428 F...m pipewire /dev/snd/pcmC3D0p: widders 6428 F...m pipewire /dev/snd/pcmC0D9p: widders 6428 F...m pipewire /dev/snd/seq: widders 6428 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 23:40:46 2026 InstallationDate: Installed on 2018-11-14 (2876 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwDevWlp11s0Link: Not connected. MachineType: ASUS System Product Name 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-34-generic root=UUID=86127bef-7d71-4426-8373-82798d2c8063 ro rootflags=subvol=@ quiet splash intel_iommu=on snd-hda-intel.snoop=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-01 (90 days ago) dmi.bios.date: 12/14/2023 dmi.bios.release: 18.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X670E-E GAMING WIFI 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.:bvr1807:bd12/14/2023:br18.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX670E-EGAMINGWIFI: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 modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-06-29T02:14:01.068739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168825/+subscriptions
[Bug 2166838] Re: [SRU] Fix for storage corruption on 64 bit DMA on AMD platforms
Patches for Resolute: https://lists.ubuntu.com/archives/kernel-team/2026-September/172562.html (Also working on patches for Noble) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166838 Title: [SRU] Fix for storage corruption on 64 bit DMA on AMD platforms Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Resolute: New Bug description: https://bugs.launchpad.net/bugs/2166838 [ Impact ] We found a issue where if our BIOS enables certain enhanced features for PCIe atomics for PCI root port on a system where some devices don't support, it leads to malfunction on some of those devices. Currently this manifests as storage corruption on PCIe-connected SATA storage, but potentially can lead to more general PCIe device issues. [ Fix ] Cherry-pick a quirk for AMD platforms from this patcheset: - Fix for storage corruption w/ AMD IOMMU on 64-bit addressing[1] They can be found in following commits: 1. 4fde4482 (mainline) x86/PCI: Disable enhanced atomics on AMD NBIO 7.7 and 7.11 2. 6b28e0e7 (linux-next) Revert "ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585" And a dependent patch to make these 2 apply cleanly: 1. 21e7b971 (mainline) ata: Use named initializers for pci_device_id arrays This dependent patch simply cosmetic (e.g. replace struct initialization with designated initializer) and functionally should make no difference before and after. [ Test plan ] Install the kernel with the said fix, and run workload on the PCIe storage to deplete 32bit DMA address for the given storage. When the PCIe The storage start using 64 bit DMA address, content of that storage shouldn't be corrupted. [ Where problems could occur ] The quirk is AMD-specific. This disables certain enhancement feature on PHX/HPT/STX/KRK/STXH platforms. Normal PCIe AtomicOp should not get impacted. Although this is more of a BIOS issue, it's unlikely to get BIOS update for all those platforms in the field. So adding a quirk in kernel would help mitigate that. [ Additional Information ] [1] https://lore.kernel.org/linux- ide/20260908190600.226485-1-mario.limonciello@amd.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166838/+subscriptions
[Bug 2168783] Re: Regression in 7.0.0-31/-34: GPF in path_is_under() leaks mount_lock, system hard-freezes
** 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/2168783 Title: Regression in 7.0.0-31/-34: GPF in path_is_under() leaks mount_lock, system hard-freezes Status in linux package in Ubuntu: New Bug description: Since linux 7.0.0-31 (and still in 7.0.0-34) the machine hard-freezes within ~10-25 minutes of normal desktop use. 7.0.0-29 and 7.0.0-30 are unaffected; 7.0.0-15 had the same bug. Sequence, identical every time: 1. Oops (GPF on non-canonical address, or page fault at fffffffffffffff0) at path_is_under+0x50/0x90, reached from a plain newfstatat(): path_is_under <- complete_walk <- path_lookupat <- filename_lookup <- vfs_statx <- vfs_fstatat <- __do_sys_newfstatat Triggering task is a GLib worker thread (Comm: pool-2 / localsearch-3, the GNOME file indexer). 2. The task dies inside the read_seqlock_excl(&mount_lock) critical section ("exited with preempt_count 1" / "exited with irqs disabled"), so mount_lock is never released. 3. Every later task that touches mounts spins in native_queued_spin_lock_slowpath: soft lockups on systemd, chrome, bwrap, runc (mntput_no_expire_slowpath, drm_release), then RCU stalls, then total freeze. Boot history on this machine (same NVIDIA 595.71.05 DKMS driver throughout): 7.0.0-15: 5 of 8 boots froze 7.0.0-29 / -30: 26 boots, 0 faults (18 with the indexer running) 7.0.0-31: 2 of 3 boots froze 7.0.0-34: froze 22 min after re-enabling localsearch-3 Reproduce: boot 7.0.0-34 with localsearch-3 enabled and use the desktop normally (browser, Docker/bwrap sandboxes); freeze within ~25 min. Masking localsearch-3 avoids it. The full kernel log from the crashed boot is attached to the report as CrashBootKernelLog. Hardware: ASUS ROG STRIX Z690-I, BIOS 4505. Ubuntu 26.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168783/+subscriptions
[Bug 2168799] Re: Complete System shutdown via disconnecting from Power needed
** 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/2168799 Title: Complete System shutdown via disconnecting from Power needed Status in linux package in Ubuntu: New Bug description: I tried to use Cycles and GPU Compute in Blender and my whole System breaks. I got an Blackscreen and cant reset via the reset button and so i had to restart by turning off the Powerbutton of the Computer and turn it on an start my computer again. This happened all the Time no matter if opengl or vulkan is enabled. I got an Radeon RX9060XT Graphicscard and i guess it has to do with the drivers for amd, but thats just guess... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2168799/+subscriptions
[Bug 2168698] Re: Keeps freezing
** 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/2168698 Title: Keeps freezing Status in linux package in Ubuntu: New Bug description: My Ubuntu keeps freezing and I can't find the reason. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ilia 4416 F.... wireplumber /dev/snd/controlC0: ilia 4416 F.... wireplumber /dev/snd/controlC2: ilia 4416 F.... wireplumber /dev/snd/seq: ilia 4397 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 28 01:11:08 2026 InstallationDate: Installed on 2026-08-12 (46 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS All Series 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-34-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash intel_idle.max_cstate=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: 12/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd12/08/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll:pfaASUSMB: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All 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/2168698/+subscriptions
[Bug 2129564] Re: Acer nitro 16s AI makes filesystem emergency ro after suspend
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/2129564 Title: Acer nitro 16s AI makes filesystem emergency ro after suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot run ubuntu-bug linux after the system is read only; it crashes. However, the system is the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2129554 which has ubuntu-bug as it was executed before suspend. I also cannot make the system read-write again: e2fsck /dev/mapper/ubuntu--vg-ubuntu--lv e2fsck 1.47.2 (1-Jan-2025) /dev/mapper/ubuntu--vg-ubuntu--lv: recovering journal Error reading block 12160538 (Input/output error). Ignore error<y>? cancelled! /dev/mapper/ubuntu--vg-ubuntu--lv: Input/output error while reading block 12160538 JBD2: Failed to read block at offset 69146 e2fsck: Input/output error while recovering journal of /dev/mapper/ubuntu--vg-ubuntu--lv e2fsck: unable to set superblock flags on /dev/mapper/ubuntu--vg-ubuntu--lv I attach dmesg.txt after a suspend -> unsuspend Ubuntu 25.10 Linux acer 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:00:33 UTC 2025 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-5-generic 6.17.0-5.5 ProcVersionSignature: Ubuntu 6.17.0-5.5-generic 6.17.0-rc7 Uname: Linux 6.17.0-5-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 22 17:04:34 2025 InstallationDate: Installed on 2025-10-19 (3 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: Acer Nitro AN16S-61 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=/vmlinuz-6.17.0-5-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 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2025 dmi.bios.release: 1.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EV3_SKF dmi.board.vendor: SXP dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.03:bd04/30/2025:br1.3:efr1.4:svnAcer:pnNitroAN16S-61:pvrV1.03:rvnSXP:rnEV3_SKF:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 16S AI dmi.product.name: Nitro AN16S-61 dmi.product.sku: 0000000000000000 dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2129564/+subscriptions