From owner-freebsd-arm@freebsd.org Thu Aug 20 22:39:21 2015 Return-Path: Delivered-To: freebsd-arm@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 C6AFD9BEAE9 for ; Thu, 20 Aug 2015 22:39:21 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A805199D; Thu, 20 Aug 2015 22:39:21 +0000 (UTC) (envelope-from onwahe@gmail.com) Received: by igui7 with SMTP id i7so2111472igu.0; Thu, 20 Aug 2015 15:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3rBozdSvHLRWtCdXo8sCuHK/iavy7ObCG2oNM6n58rs=; b=qeJHu34izvSC5tXJyu6IldNbFwbOmQy25Q4c+QBLRQpGkTOuS5enNp9PMEPsZeVCV7 z/0VCFPiYodITe21d3yhpk4Cj7kCGARvAh4I+hk/s2ZfRWoTdGzycme3lYKEpbHDjM3L 0bwC//noNzLDkv8Rkh3BU55FlM8zEoW0mE6ZE3Zo+x64BN9XH6wkgn3jcC2YX7iZAjin htZYUNigK3lDMiEsuNBgetD7bgIguOkswajwQi80TFBH07SeLQ+QpO1FyLkDmHcYaw5E ZkSzDPV67YiSKgJFJC2xByvBh/239PHdBv0ja9TCHU9NEmjKjhMisDsizI89SfzEyhoR 8ilA== MIME-Version: 1.0 X-Received: by 10.50.178.144 with SMTP id cy16mr433393igc.26.1440110361114; Thu, 20 Aug 2015 15:39:21 -0700 (PDT) Received: by 10.64.239.196 with HTTP; Thu, 20 Aug 2015 15:39:20 -0700 (PDT) In-Reply-To: <20150820201020.GC1245@hades.panopticon> References: <20150819013834.GD79354@hades.panopticon> <20150819120753.GH79354@hades.panopticon> <20150819134708.GJ79354@hades.panopticon> <20150819232836.GA1245@hades.panopticon> <20150820185417.GB1245@hades.panopticon> <20150820201020.GC1245@hades.panopticon> Date: Fri, 21 Aug 2015 00:39:20 +0200 Message-ID: Subject: Re: Instability likely related to new pmap on Cubieboard A10 From: Svatopluk Kraus To: Dmitry Marakasov Cc: Adrian Chadd , "freebsd-arm@FreeBSD.org" , Ian Lepore Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2015 22:39:21 -0000 On Thu, Aug 20, 2015 at 10:10 PM, Dmitry Marakasov wrote: > * Svatopluk Kraus (onwahe@gmail.com) wrote: > >> >> If it helps, set it again to 1 and try attached patch, please. >> >> >> >> If neither the first nor the seconf attemp will work, can you send me >> >> output like before but from another panic. I would like to see >> >> diference. >> > >> > Just for the case, with patch and sp_enabled back to 1: >> > >> > https://people.freebsd.org/~amdmi3/pmap3.log >> > >> >> Thanks. Meantime, I tried most recent HEAD on pandaboard and >> beaglebone black and no problem there. Do you have enabled INVARIANTS >> and INVARIANT_SUPPORT in your config? > > I've enabled them at some point - at least last two runs had these > enabled. Any other way I could help? Maybe I should check if it was > new pmap commit which caused this, and if not, bisect it? > Yes, if you know that some revision of kernel was working, it would be nice to confirm that. Next thing is, with KTR option enabled, set mask to KTR_TRAP only and get me output from "show ktr" after panic or freeze if you can get to kdb. This way we will know addresses which cause segmentation faults. Svata