On Mon, 3 Aug 2026 at 09:03, Adrian Chadd <[email protected]> wrote: > > On Mon, 3 Aug 2026 at 07:48, Klaus Küchemann <[email protected]> > wrote: > > > > Hi, > > > > unfortunately rebuilt port drm-66-kmod (directly from Makefile inside the > > work-directory) & reinstalling > > didn`t help. It’s the port(tested) that triggers the boot panic...Or am I > > missing an unknown patch for the version mismatch? > > > > Well, in the past drm graphics sometimes worked under main/current & > > sometimes did not but never panicked on boot... > > > > Have absolutely no clue what could trigger the > > > > > >> > > >> Panic String: Assertion td->td_lkpi_task == NULL failed at > > >> /usr/src/sys/compat/linuxkpi/common/src/linux_current.c:85 > > I may have missed it; what's the full backtrace here?
Ah, I found it: >> panic() at panic+0x43/frame 0xfffffe01392cc3c8 >> linux_alloc_current() at linux_alloc_current+0x2e3/frame 0xfffffe01392cc418 >> dc_assert_fp_enabled() at dc_assert_fp_enabled+0x77/frame 0xfffffe01392cc438 >> dcn21_update_bw_bounding_box() at dcn21_update_bw_bounding_box+0x26/frame >> 0xfffffe01392cc470 >> dc_create() at dc_create+0x3c4/frame 0xfffffe01392cc4b0 >> dm_hw_init() at dm_hw_init+0x45e/frame 0xfffffe01392cc6d0 >> amdgpu_device_ip_hw_init_phase2() at >> amdgpu_device_ip_hw_init_phase2+0x5a/frame 0xfffffe01392cc700 If you're absolutely sure you're running the most recent -head and drm-66 build, then I'd file a bug. My local machines were just updated to: ``` commit 16e47f317c4ce2be5fed530bf8a9af9f9bf55364 (upstream/main, upstream/HEAD) Author: Gleb Popov <[email protected]> Date: Mon Jul 27 21:18:12 2026 +0300 nuageinit: Allow the userdata script to run before firstboot* rc services ``` and ``` drm-66-kmod-6.6.25.1600019_10 Direct Rendering Manager (DRM) GPU drivers ``` But it's very possible that your amdgpu is taking a different setup path to mine. Mine loads 'green_sardine' firmware blobs, is an AMD Ryzen 7 7730U chipset. -adrian
