Date: Sat, 20 Oct 2018 02:10:52 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org> Subject: =?UTF-8?Q?DRM=3a_radeonkms_=e2=80=a6_can_not_be_unloaded_=28kernel_?= =?UTF-8?B?cGFuaWMpKSDigKY=?= Message-ID: <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com> In-Reply-To: <f25e294a-192a-04f9-2466-d1fe09b32fec@gmail.com> References: <f25e294a-192a-04f9-2466-d1fe09b32fec@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20/10/2018 00:01, Graham Perrin wrote: > kldunload radeonkms > > – results in a kernel panic. Found, at <https://github.com/FreeBSDDesktop/kms-drm/issues/90#issuecomment-415859021>; under 'drm-devel-kmod g20180822 screen freeze': >> … normally you never unload the graphics driver so we haven't spent time on proper cleanup. Also, the drm module will cause panic if you try load load it again after unload. ---- Is the principle for -next- the same as for -devel-, should I simply _never_ attempt to unload the module? $ date ; uname -v Sat 20 Oct 2018 02:06:21 BST FreeBSD 12.0-BETA1 r339438 GENERIC $ pkg query '%o %v %R' drm-kmod drm-next-kmod gpu-firmware-kmod graphics/drm-next-kmod 4.11.g20180822 poudriere graphics/gpu-firmware-kmod g20180825 FreeBSD $
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?29c87b89-2de0-fc72-4591-e362fd965322>