Date: Tue, 04 Aug 2026 00:57:28 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 297250] graphics/drm-66-kmod (amdgpu): panic: Assertion td->td_lkpi_task == NULL Message-ID: <bug-297250-7141-gNBEODcqWu@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-297250-7141@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297250 --- Comment #4 from Klaus Küchemann <maciphone2@googlemail.com> --- (In reply to rkoberman from comment #3) <<A significant difference is that I was running 612, not 66>> Yes, /usr/ports/graphics/drm-kmod last but not least also chooses 612 for my system and is running fine now. No clue how 66 came to the system in the past.. that`s why I think(or guess) that: — pkg delete [everything drm-kmod & gpu-firmware-kmod] pkg autoremove cd /usr/ports/graphics/drm-kmod make install cd /usr/ports/graphics/gpu-firmware-kmod make install — is hopefully a safe workaround for now for everyone, regardless the current head version(which here was 1600019 ). Also the mentioned mismatch warning (graphics/drm-66-kmod/files/pkg-message.in ) said(or maybe lied:-) that my OS-version is O.K. I`m not aware of the code-related details of the real root cause of this bug And a PR on phab or git for correction of pkg-message.in would also not prevent anybody from running into this trap because that message comes too late(after polluting the system) (and is even wrong). Regards -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-297250-7141-gNBEODcqWu>