Date: Sun, 21 Oct 2018 08:44:21 -0600 From: Warner Losh <imp@bsdimp.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: Hans Petter Selasky <hps@selasky.org>, Graham Perrin <grahamperrin@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: =?UTF-8?B?UmU6IERSTTogcmFkZW9ua21zIOKApiBjYW4gbm90IGJlIHVubG9hZGVkIChrZXJuZWwgcA==?= =?UTF-8?B?YW5pYykpIOKApg==?= Message-ID: <CANCZdfpsdOr5wnN1CRt8RYGau%2BoRRGwefo259p1QhGQ0u9fpjg@mail.gmail.com> In-Reply-To: <CAN6yY1tTcBpnrRDFz6Ox1tJixVM-KkCt-TmZ3z=heV-%2B=Ck_yw@mail.gmail.com> References: <f25e294a-192a-04f9-2466-d1fe09b32fec@gmail.com> <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com> <c2a4cf6d-d9c5-6e76-ef21-de0740f0e91e@selasky.org> <CAN6yY1tTcBpnrRDFz6Ox1tJixVM-KkCt-TmZ3z=heV-%2B=Ck_yw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 21, 2018, 2:29 AM Kevin Oberman <rkoberman@gmail.com> wrote: > On Sat, Oct 20, 2018 at 1:28 AM Hans Petter Selasky <hps@selasky.org> > wrote: > > > On 10/20/18 3:10 AM, Graham Perrin wrote: > > > On 20/10/2018 00:01, Graham Perrin wrote: > > > > > >> kldunload radeonkms > > >> > > >> =E2=80=93 results in a kernel panic. > > > > > > Found, at < > > > https://github.com/FreeBSDDesktop/kms-drm/issues/90#issuecomment-41585902= 1 > > > > under 'drm-devel-kmod g20180822 screen freeze': > > > > > >>> =E2=80=A6 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 tr= y > > 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 yo= u > > 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. Eve= n > if you install packages for your release, you need to realize that packag= es > are built against the oldest supported minor release of a major release a= nd > 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 mino= r > release where people who have broken systems can get trusted packages. So= me > 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@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpsdOr5wnN1CRt8RYGau%2BoRRGwefo259p1QhGQ0u9fpjg>