Date: Wed, 30 Dec 2020 06:05:37 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 250193] Kernel panic loading DRM kmods Message-ID: <bug-250193-7141-3VxGgJg8r9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250193-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-250193-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250193 rkoberman@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rkoberman@gmail.com --- Comment #8 from rkoberman@gmail.com --- This is a well known problem. While the system ABI is fixed for the life of= a major release, the KBI is not guaranteed stable. Specifically, there was a significant change in the lkpi code used for graphics drivers and, as a res= ult, drm-*-kmod packages for 12.1 will not work on 12.2. Full stop! The only solution is to build a package on a 12.2 system with the full sour= ces for/usr/src/sys. (cd /usr/ports/graphics/drm-fbsd12.0-kmod && make package) Once that package is built (in /usr/ports/packages/All), it may be copied to other 12.2-RELEASE systems with the same arch with "pkg add". This may apply to other ports that build kmods and the same issue hit virtualbox-ose-kmod in 11.something. I'm pretty sure I was bitten by one ot= her case, but I don't recall when. It seems like a trivial solution is to make a set of trusted packages of ev= ery kmod port for each minor release after .0, sign them, and make them availab= le. I am still baffled why this has not happened. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250193-7141-3VxGgJg8r9>