[Bug 297250] graphics/drm-66-kmod (amdgpu): panic: Assertion td->td_lkpi_task == NULL
[email protected] Thu, 06 Aug 2026 22:08:34 +0000
| Newsgroups | gmane.os.freebsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297250 --- Comment #5 from [email protected] --- My battle continues with no improvement. I have deleted all drm-kmod and gpu-firmware-* software, done pkg autoremove and reinstalled drm-612-kmod and gpu-firmware-intel-kmod. Nothing improved. With drm-612-kmod, attempting to run mpv resulted in a GPU lockup as soon as the video tried to start playing. No other messages were displayed or logged. Repeated except install drm-66-kmod. Again no change from that kmod in the past. Difference from 612 ias that the GPU does not lock up. Instead I get three of the error: [vo/gpu-next/libplacebo] Masking `storable` from wrapped texture because the corresponding format 'bgra8' does not support PL_FMT_CAP_STORABLE followed by a long stream of [vo/gpu-next/libplacebo] vkQueueSubmit2: VK_ERROR_UNKNOWN (../src/vulkan/command.c:533) I should note that, until the recent update of mesa, MPV simply reported that vulkan was not functional and played the video, probably using vaapi. I think the problem stems from mesa being fixed but drm-kmd (either 66 or 612 being broken, but in different ways. Another thing that locks up 615 is virtualbox. If I start or save a VM, part way through the operation, the GPU locks up. If a switch to another workspace, it does not happen. It either starts or saves normally. System is 12th Gen Intel(R) Core(TM) i5-1235U (2496.00-MHz K8-class CPU) GPU is Intel: vgapci0@pci0:0:2:0: class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086 device=0$ vendor = 'Intel Corporation' device = 'Alder Lake-UP3 GT2 [Iris Xe Graphics]' I have multiple tools written to use mpv capability not available elsewhere and I have been unable to figure a way to write it for vlc as it lacks the capability to use a UNIX pipe to talk to it while still having keyboard access. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.