Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Aug 2026 22:31:00 +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-cT8jfOQlZq@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 #1 from Klaus Küchemann <maciphone2@googlemail.com> ---

well, in the end I could workaround this bug  by trial&error in the following
sequence :
1. — solution (important to install BOTH drm&firmware via ports)—
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

Maybe the above is a known sequence for some people who hit this issue but why
not fix this bug

2.—while worked around it  for now  I think I’ll leave this bugzilla open since
the following related is for sure a kernel bug  :

This should be the (existing)correct way to prevent kernel crash/attack: 
root@fbsd5pro:~ # kldunload  amdgpu_renoir_asd_bin.ko
kldunload: can't unload file: Device busy
…with the addition of console-message :
kldunload: attempt to unload file that was loaded by the kernel

But :
 try to:
 kldunload amdgpu,
 ouch, massive crash(system tries to goto init1 and even fails that attempt &
freezes)

3.—
Also I would suggest to „ forbid“ to install drm-kmod & gpu-firmware-kmod via
pkg 
since version incompatibilities or whatever crap will massively pollute the
system and will crash X11 or kernel panic  .
Instead an attempt of using pkg should ONLY spit out a warning message AND
instructions to do it correctly via ports.
I know there is a message AFTER(why not before?) installation like :
If not good for your OS- version then rebuild ( w/o details howto remove the
crap and rebuild)
of course: fix instead of warn is even better :-)


O.K., above only as a conceptual approach , for me it’s fixed thanks to some
hints from the mailing list, thx :-)
.. if someone wants to close this report, O.K. for me

Thx @Mark Linimon for redirecting this to X11@ , Regards

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee 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-cT8jfOQlZq>