Re: Recent -CURRENT and drm-66-kmod panic
- Reply: Roman Bogorodskiy : "Re: Recent -CURRENT and drm-66-kmod panic"
- In reply to: Roman Bogorodskiy : "Re: Recent -CURRENT and drm-66-kmod panic"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 12 Mar 2026 17:12:44 UTC
Am 11.03.26 um 18:30 schrieb Roman Bogorodskiy: > Roman Bogorodskiy wrote: > >> Rainer Hurling wrote: >> >>> Am 27.02.26 um 18:16 schrieb Roman Bogorodskiy: >>>> Hi, >>>> >>>> I've updated my and of January -CURRENT to today's version >>>> (c3577fcf3fd0494cc992021d4debbca09241a49e), rebuilt >>>> graphics/drm-66-kmod which is now at: >>>> >>>> Version : 6.6.25.1600011_8 >>>> >>>> System crashes during boot, full crash info is here: >>>> >>>> https://people.freebsd.org/~novel/misc/core-drm-66-kmod-6.6.25.1600011.txt >>>> >>>> Things work fine when booting the old kernel, even without rebuilding >>>> the drm-66-kmod. >>>> >>>> Is that a known issue? >>>> >>>> Roman >>>> >>> >>> Hmm, just a guess: >>> Did you also rebuild something like graphics/gpu-firmware-intel-kmod? >> >> No, I didn't rebuild graphics/gpu-firmware-intel-kmod, only >> graphics/drm-66-kmod. >> >> In the meantime I've opened an issue here: >> >> https://github.com/freebsd/drm-kmod/issues/419 >> >> And as I commented there, the issue starts showing up for me with >> freebsd-src commit 79b05e7f80eb482287c700f10da9084824199a05. >> >> I will check if rebuilding graphics/gpu-firmware-intel-kmod makes any >> difference. >> >>> HTH, >>> Rainer >>> > > Just did a quick test. > > - checked out latest -CURRENT (ff2c98b30b57b9763e2a6575f729bab676e6c025) > - build && reboot --> the same panic as before > - reverted 79b05e7f80eb482287c700f10da9084824199a05 > - build && reboot --> system works fine > > Didn't rebuild drm-66-kmod and related ports. > > Roman Is there a reason why you didn't try the latest CURRENT version together with newly built graphics/gpu-firmware-intel-kmod and drm-66-kmod related ports? Sorry if I overlooked something. Rainer