From owner-freebsd-current@freebsd.org  Sat Oct 20 07:52:02 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 262EAFFCA60
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat, 20 Oct 2018 07:52:02 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BF50F82D8B
 for <freebsd-current@freebsd.org>; Sat, 20 Oct 2018 07:52:01 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [178.17.145.230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 4EBC02602B3;
 Sat, 20 Oct 2018 09:51:53 +0200 (CEST)
Subject: =?UTF-8?Q?Re=3a_DRM=3a_radeonkms_=e2=80=a6_can_not_be_unloaded_=28k?=
 =?UTF-8?B?ZXJuZWwgcGFuaWMpKSDigKY=?=
To: Graham Perrin <grahamperrin@gmail.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
References: <f25e294a-192a-04f9-2466-d1fe09b32fec@gmail.com>
 <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <c2a4cf6d-d9c5-6e76-ef21-de0740f0e91e@selasky.org>
Date: Sat, 20 Oct 2018 09:51:23 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.0.1
MIME-Version: 1.0
In-Reply-To: <29c87b89-2de0-fc72-4591-e362fd965322@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2018 07:52:02 -0000

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