From owner-freebsd-hackers@freebsd.org Wed Feb 22 05:29:15 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 8ADE0CE963E; Wed, 22 Feb 2017 05:29:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 EEA3D1F27; Wed, 22 Feb 2017 05:29:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v1M5T8f6096325 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 22 Feb 2017 07:29:08 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v1M5T8f6096325 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v1M5T84R096324; Wed, 22 Feb 2017 07:29:08 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 22 Feb 2017 07:29:08 +0200 From: Konstantin Belousov To: Steve Kargl Cc: Mateusz Guzik , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: drm2, i915kms cause instant lock-up Message-ID: <20170222052908.GL2092@kib.kiev.ua> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170221185511.GA98080@troutmask.apl.washington.edu> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home 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:29:15 -0000 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 ? 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. If such kernel does not boot, I will provide further instructions.