Date: Wed, 30 Dec 2020 14:15:47 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 250193] Kernel panic loading DRM kmods Message-ID: <bug-250193-7141-RiUyFsy2Vy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250193-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=250193 --- Comment #9 from Jason W. Bacon <jwb@freebsd.org> --- (In reply to Jason W. Bacon from comment #7) I have to retract the claim that the binary drm-kmod packages were working on my MacBook. I'm sure I was using modesetting successfully after the fresh install, but I did not confirm that it was using drm-kmod from ports. It may have failed to load it and later auto-loaded the legacy modules in /boot/kernel. Since running freebsd-update, neither driver is working and it's falling back on scfb. When trying to use the ati driver, there's a lot of chatter about Radeon in Xorg.0.log, but it ultimately fails and falls back to scfb. This may have been the case before the upgrade as well. Loading i915kms built from source causes the console to freeze during boot. The system is still operational and tapping the power button shuts down gracefully. At any rate, the scfb driver performs fine for my purposes. I also wondered if we should generate packages for a new point release, just for special cases like this. Most of the 12.1 packages are fine on 12.2, but maybe we could tag ports like drm-kmod* to build separately on new point releases during the overlap period. I'm not sure we have the means to guarantee issues like this won't happen again in the future, so it would seem prudent to have processes in-place to mitigate it. -- 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-250193-7141-RiUyFsy2Vy>