From owner-freebsd-x11@freebsd.org Mon Sep 24 13:24:23 2018 Return-Path: Delivered-To: freebsd-x11@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 1C6FF10AC0E7 for ; Mon, 24 Sep 2018 13:24:23 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 882E78093A for ; Mon, 24 Sep 2018 13:24:22 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([92.134.114.191]) by mwinf5d56 with ME id fRQK1y00y47q9Nc03RQKXV; Mon, 24 Sep 2018 15:24:20 +0200 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Mon, 24 Sep 2018 15:24:20 +0200 X-ME-IP: 92.134.114.191 To: FreeBSD-x11@FreeBSD.org From: Claude Buisson Subject: drm-[stable|next]-kmod and MAXCPU Message-ID: Date: Mon, 24 Sep 2018 15:24:19 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.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.27 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, 24 Sep 2018 13:24:23 -0000 Hello, I tried to switch an amd64 Ivy Bridge system (with STABLE-11 @ r338696), from drm2 in base to drm-stable-kmod (and also drm-next-kmod) in ports, after rebuilding the custom kernel without any drm/drm2 module. I installed: gpu-firmware-kmod-g20180825 drm-stable-kmod-g20180822 (and also tried: drm-next-kmod-g20180822 with the same results) Loading "by hand", by rc.conf, or by loader.conf i915kms.ko led to an immediate reboot. I built a GENERIC kernel (without any drm/drm2 module), and everything was OK. So I tried modifying the GENERIC kernel and came to that conclusion: the drm-[stable|next]-kmod ports cannot be used with a kernel built with MAXCPU (at least not defined as 256)!! I commented the MAXCPU line in my custom kernel definition, and got back a working system. May be, the assumptions about kernels could be explicited for ports of this kind ?? Hoping being useful, CBu