Public bug reported: An ASUS ProArt PX13 HN7306EAC with an AMD integrated GPU (PCI ID 1002:1586) repeatedly experienced kernel-side TTM/AMDGPU corruption and complete graphical failure while running Ubuntu 26.04 kernel 7.0.0-29-generic.
The failures occurred with different visible userspace processes. They are therefore reported as possible triggers, not assumed root causes. FIRST HARD FREEZE / NULL DEREFERENCE A complete desktop freeze required a hard reset. The first fatal event was: BUG: kernel NULL pointer dereference, address: 0000000000000019 Comm: ptyxis RIP: ttm_lru_bulk_move_pos_tail+0x53/0xd0 [ttm] Relevant call path: ttm_resource_add_bulk_move ttm_bo_populate ttm_bo_vm_fault_reserved amdgpu_gem_fault A previous occurrence involved firefox:gl0 and failed in the same TTM/AMDGPU resource-management area. LATER TTM LIST CORRUPTION Immediately before the warnings, the kernel repeatedly logged: amdgpu_vm_validate() failed. Not enough memory for command submission! This was followed by: list_add corruption list_del corruption Relevant call paths included: ttm_resource_move_to_lru_tail ttm_bo_populate ttm_bo_vm_fault_reserved amdgpu_gem_fault and: ttm_resource_fini ttm_resource_free amdgpu_bo_move amdgpu_cs_bo_validate amdgpu_cs_ioctl LATER GRAPHICAL-SESSION FAILURE AMDGPU again rejected command submissions with -12. GNOME Shell then aborted with SIGABRT in Mesa Gallium, closing the Wayland session and all terminal applications. This event was a graphical-session restart, not a full machine reboot. ENVIRONMENT Hardware: ASUS ProArt PX13 HN7306EAC CPU/GPU: AMD Ryzen AI Max+ 395 / Radeon 8060S GPU PCI ID: 1002:1586 BIOS: HN7306EAC.307 (2026-01-27) RAM: 128 GB shared system/GPU memory Distribution: Ubuntu 26.04 Kernel: 7.0.0-29-generic, package 7.0.0-29.29 (upstream base 7.0.12) Desktop: GNOME on Wayland WORKLOAD / POSSIBLE TRIGGER Local llama.cpp/Vulkan language-model workloads and desktop applications were active. They use shared system/GPU memory and may increase memory pressure. This is reported as a possible trigger only, not as a demonstrated root cause. NEGATIVE EVIDENCE The inspected logs before the first Oops did not show an OOM kill, MCE, thermal shutdown, PCIe AER error, GPU ring timeout, or GPU reset. The kernel was not tainted before the first Oops. EXPECTED RESULT Userspace GPU activity or memory pressure must not corrupt TTM lists, trigger a kernel NULL pointer dereference, or terminate the graphical session. PRIVACY No vmcore, dump-incomplete, or full memory image is attached because those artifacts may contain credentials, documents, medical data, and browser contents. RELATED REPORT A public report with a similar ttm_lru_bulk_move_pos_tail signature and hard desktop freeze is available at: https://github.com/basecamp/omarchy/issues/6443 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2163363 Title: [amdgpu/ttm] TTM list corruption and NULL dereference under GPU memory pressure on ASUS ProArt PX13 (7.0.0-29) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163363/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
