From owner-freebsd-current@freebsd.org Tue Feb 19 19:18:11 2019 Return-Path: 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 A945914FA160; Tue, 19 Feb 2019 19:18:11 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 787346E737; Tue, 19 Feb 2019 19:18:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id x1JJI84N003134 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 19 Feb 2019 11:18:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x1JJI8f0003128; Tue, 19 Feb 2019 11:18:08 -0800 (PST) (envelope-from sgk) Date: Tue, 19 Feb 2019 11:18:07 -0800 From: Steve Kargl To: Johannes Lundberg Cc: "freebsd-hackers@freebsd.org" , freebsd-current@freebsd.org Subject: Re: What is evdev and autoloading? Message-ID: <20190219191807.GA2941@troutmask.apl.washington.edu> Reply-To: sgk@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 787346E737 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.10 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; TO_DN_SOME(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_IN_DNSWL_MED(-0.20)[21.76.95.128.list.dnswl.org : 127.0.11.2]; MX_GOOD(-0.01)[cached: troutmask.apl.washington.edu]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.07)[ip: (0.13), ipnet: 128.95.0.0/16(0.19), asn: 73(0.09), country: US(-0.07)]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.87)[0.871,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[washington.edu]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.974,0]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.50)[0.497,0]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2019 19:18:11 -0000 On Tue, Feb 19, 2019 at 06:59:26PM +0000, Johannes Lundberg wrote: > > On 2/19/19 5:35 PM, Steve Kargl wrote: >> On Tue, Feb 19, 2019 at 08:17:48AM -0800, Cy Schubert wrote: >>> >>> Drm2 is not required. My current laptop is 5 years old, an HD3000. The previous one is 13 years old, i915. Both work perfectly with drm-current on 13-current. Franky, I don't see what the fuss is about. >>> >>> >> 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. -- Steve