From owner-freebsd-x11@freebsd.org Mon Sep 18 13:19:24 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D43CE0F9D8; Mon, 18 Sep 2017 13:19:24 +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 620D168146; Mon, 18 Sep 2017 13:19:20 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (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 B12CF26034B; Mon, 18 Sep 2017 15:19:12 +0200 (CEST) To: FreeBSD Current , "freebsd-x11@FreeBSD.org" , Mark Johnston , "kwm@freebsd.org" , jmd@FreeBSD.org From: Hans Petter Selasky Subject: [HEADS UP] Update of graphics/drm-next-kmod is required after FreeBSD r323702 Message-ID: <67457171-5a50-bdeb-d371-1c5aa1017c17@selasky.org> Date: Mon, 18 Sep 2017 15:16:45 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2017 13:19:24 -0000 Hi, If you are using the drm-next-kmod from ports, don't upgrade your kernel beyond r323702 until the drm-next-kmod port has been updated. There are some changes planned for the LinuxKPI which can lead to memory leaks if you mix the versions together. Rebuilding the drm-next-kmod module is not enough to fix this. Possibly a FreeBSD kernel version check should be added to drm-next-kmod before building after the planned update. Thank you for the attention. --HPS