From owner-freebsd-hackers@freebsd.org Wed Feb 20 16:07:43 2019 Return-Path: Delivered-To: freebsd-hackers@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 03FCB14F79DE; Wed, 20 Feb 2019 16:07:43 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay114.isp.belgacom.be (mailrelay114.isp.belgacom.be [195.238.20.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 087EC867AD; Wed, 20 Feb 2019 16:07:41 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BdAABjem1c/99MQFdkDg4BAQEEAQE?= =?us-ascii?q?HBAEBgVEHAQELAQGCAlZiMieMIV+LCgEBggw1AYlwjXaBe4R5AoNzIzQJDQE?= =?us-ascii?q?DAQECAQECbShCARABhHcBBTocIxALDgoJJQ8qHgYThRevAYkngQ6MW4F/hCO?= =?us-ascii?q?KYQKRF5I1CZJOJZMGnjk4gVZNMAiDJ4IoF41jPD4DMAGFJopkAQE?= X-IPAS-Result: =?us-ascii?q?A2BdAABjem1c/99MQFdkDg4BAQEEAQEHBAEBgVEHAQELA?= =?us-ascii?q?QGCAlZiMieMIV+LCgEBggw1AYlwjXaBe4R5AoNzIzQJDQEDAQECAQECbShCA?= =?us-ascii?q?RABhHcBBTocIxALDgoJJQ8qHgYThRevAYkngQ6MW4F/hCOKYQKRF5I1CZJOJ?= =?us-ascii?q?ZMGnjk4gVZNMAiDJ4IoF41jPD4DMAGFJopkAQE?= Received: from 223.76-64-87.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([87.64.76.223]) by relay.skynet.be with ESMTP; 20 Feb 2019 17:07:41 +0100 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id x1KG7d1S042574; Wed, 20 Feb 2019 17:07:39 +0100 (CET) (envelope-from tijl@FreeBSD.org) Date: Wed, 20 Feb 2019 17:07:38 +0100 From: =?UTF-8?B?VMSzbA==?= Coosemans To: Steve Kargl Cc: Johannes Lundberg , "freebsd-hackers@freebsd.org" , freebsd-current@freebsd.org Subject: Re: What is evdev and autoloading? Message-ID: <20190220170738.37181f94@kalimero.tijl.coosemans.org> In-Reply-To: <20190219191807.GA2941@troutmask.apl.washington.edu> References: <201902181650.x1IGoRsZ006131@pdx.rh.CN85.dnsmgr.net> <11a49d72-3158-1b9a-f933-6702d8f5c238@nomadlogic.org> <362D8283-0B7D-402F-99CD-657021597955@cschubert.com> <20190219173554.GA1066@troutmask.apl.washington.edu> <20190219191807.GA2941@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 087EC867AD X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.95 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.95)[-0.951,0]; ASN(0.00)[asn:5432, ipnet:195.238.0.0/19, country:BE] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2019 16:07:43 -0000 On Tue, 19 Feb 2019 11:18:07 -0800 Steve Kargl wrote: > On Tue, Feb 19, 2019 at 06:59:26PM +0000, Johannes Lundberg wrote: >> On 2/19/19 5:35 PM, Steve Kargl wrote: >>> My Dell Latitude D530 running i386 freebsd, which used the >>> i915kms.ko now locks up solid with drm-legacy-kmod. The PAE vs >>> non-PAE i386/conf/pmap.h merger in r342567 broke drm-legacy-kmod. >>> It seems that Niclas has provided a patch that fixes the building >>> of drm-legacy-kmod. >>> >>> Doing a bisection on /usr/src commits is fairly slow as it >>> takes a day to build world/kernel and the minimum set of ports >>> need to fire up Xorg. r343543 and earlier appear to work fine >>> with drm-legacy-kmod. >> >> So it's not only a build error, it's also a runtime bug that would have >> happened even with drm2 in base? Hmm.. > > It appears that that's the case. The likely candidates > are r343564(+65 for missing header), r343566, and r343567. That last commit added hw.above4g_allow tunable. Does it help if you set this to 0 in /boot/loader.conf? Also, it's worth trying drm-current-kmod if you haven't done so recently. If you did try already what were the problems?