Re: DRM: radeonkms … can not be unloaded (kernel panic)) …

From: Warner Losh <imp_at_bsdimp.com>
Date: Sun, 21 Oct 2018 08:44:21 -0600
On Sun, Oct 21, 2018, 2:29 AM Kevin Oberman <rkoberman_at_gmail.com> wrote:

> On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky <hps_at_selasky.org>
> wrote:
>
> > On 10/20/18 3:10 AM, Graham Perrin wrote:
> > > 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
> >
> > I recommend building these modules from source, /usr/src which match you
> > currently installed kernel!
> >
> > --HPS
> >
> This is a really good practice for all kernel modules from ports. If you
> build your kernel from source, put them into /etc/rc.conf to define
> PORTS_MODULES to always rebuild all modules when the kernel is built. Even
> if you install packages for your release, you need to realize that packages
> are built against the oldest supported minor release of a major release and
> that works or all ports that only have to match system ABIs which remain
> stable for the life of a major release. But, while the KBI (Kernel Binary
> Interface) usually remains stable, it occasionally does and did between
> 11.1 and 11.2 which meant that two ports failed when installed from
> packages on 11.2 system until 11.1 went EOL this month.
>
> I really wish that the portsmgr team would come up with a policy to
> maintain an archive of port based kernel modules whenever there is a minor
> release where people who have broken systems can get trusted packages. Some
> people are really not very capable of building from ports.
>

I've reviewed patches from jhb that rebuild when the kernel is rebuilt.
Having the package would be better but is more tricky.

Warner

--
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman_at_gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
Received on Sun Oct 21 2018 - 12:44:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:18 UTC