From owner-freebsd-hackers@freebsd.org Wed Feb 22 05:48:13 2017 Return-Path: Delivered-To: freebsd-hackers@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 07236CE9E28; Wed, 22 Feb 2017 05:48:13 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D7A4910D1; Wed, 22 Feb 2017 05:48:12 +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 v1M5mBVI004428 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 21 Feb 2017 21:48:11 -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 v1M5mBJE004427; Tue, 21 Feb 2017 21:48:11 -0800 (PST) (envelope-from sgk) Date: Tue, 21 Feb 2017 21:48:11 -0800 From: Steve Kargl To: Konstantin Belousov Cc: freebsd-hackers@freebsd.org, Mateusz Guzik , freebsd-current@freebsd.org Subject: Re: drm2, i915kms cause instant lock-up Message-ID: <20170222054811.GA4404@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170220235224.GA91194@troutmask.apl.washington.edu> <20170220235807.GC26759@dft-labs.eu> <20170221004340.GA91587@troutmask.apl.washington.edu> <20170221005030.GD26759@dft-labs.eu> <20170221052658.GA93413@troutmask.apl.washington.edu> <20170221185511.GA98080@troutmask.apl.washington.edu> <20170222052908.GL2092@kib.kiev.ua> <20170222053741.GB4204@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170222053741.GB4204@troutmask.apl.washington.edu> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 05:48:13 -0000 On Tue, Feb 21, 2017 at 09:37:41PM -0800, Steve Kargl wrote: > On Wed, Feb 22, 2017 at 07:29:08AM +0200, Konstantin Belousov wrote: > > On Tue, Feb 21, 2017 at 10:55:11AM -0800, Steve Kargl wrote: > > > On Mon, Feb 20, 2017 at 09:26:58PM -0800, Steve Kargl wrote: > > > > > > > > Well, the good news seems to be that r313254 and older are 'ok'. > > > > So, something between r313943 and r313254 is triggering a the > > > > problem. I'm still bisecting, but it might take a day or two. > > > > > > > > > > I've been able to narrow the range down to r313854 to r313943. > > > If I had to guess, the issue may be related to > > > > > > Author: kib > > > Date: Fri Feb 17 21:08:32 2017 > > > New Revision: 313898 > > > URL: https://svnweb.freebsd.org/changeset/base/313898 > > > > > > Log: > > > Merge i386 and amd64 mtrr drivers. > > > > > > I won't be able to investigate until later tonight (~ 10 hours from now). > > > > >From what I see in other messages, you are using i386 kernel on Core2 > > class machine, am I right ? Did r313897 worked fine ? Re-reading your email, I noticed you asked about r313897. I'll rebuild the kernel at this revision and r313898 and get back to to you. Yes, it is i386 on a core2 system. : FreeBSD 12.0-CURRENT #20 r313931: Tue Feb 21 21:02:18 PST 2017 root@laptop-kargl:/mnt/obj/mnt/src/sys/MOBILE i386 FreeBSD clang version 3.9.1 (tags/RELEASE_391/final 289601) (based on LLVM 3.9.1) VT(vga): text 80x25 CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (1995.04-MHz 686-class CPU) Origin="GenuineIntel" Id=0x6fd Family=0x6 Model=0xf Stepping=13 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20000000 AMD Features2=0x1 VT-x: (disabled in BIOS) HLT,PAUSE > > > > r313898 has a bug for i386 architecture, which was fixed in r313934. > > Could you compile kernel from r313898 sources with r313934 applied on > > top of it ? I mean, take r313898 and apply the changes from r313934 > > either manually or with patch, but not take any further changes from > > svn after r313898. > > > > I just completed the bisection. r313934 is the problem. > 'svn update -r 313933' boots and I can load drm2.ko. > 'svn update -r 313934' boots and hangs on loading the > module. > > As I noted in another reply I just sent, around -r313902 > I can load the i915kms.ko but console output to vt is sloooow. > Perhaps, a locking issue that 313934 exacerbated. > > -- > Steve > 20161221 https://www.youtube.com/watch?v=IbCHE-hONow > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Steve 20161221 https://www.youtube.com/watch?v=IbCHE-hONow