From owner-freebsd-arm@freebsd.org Mon Jun 29 01:11:21 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9F0F35AB33 for ; Mon, 29 Jun 2020 01:11:21 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49w8Zc4DRgz47vj for ; Mon, 29 Jun 2020 01:11:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 05T1BNA0020738 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 28 Jun 2020 18:11:24 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 05T1BNLw020737; Sun, 28 Jun 2020 18:11:23 -0700 (PDT) (envelope-from fbsd) Date: Sun, 28 Jun 2020 18:11:23 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm Subject: Re: panic: non-current pmap on RPI3 on CURRENT (GENERIC) #4 r356366 Message-ID: <20200629011123.GB10909@www.zefox.net> References: <20200108235630.GA17485@www.zefox.net> <20200109115123.GZ23031@kib.kiev.ua> <20200109172314.GA20008@www.zefox.net> <20200628195043.GA10909@www.zefox.net> <875C12B8-1E71-4808-AD3E-1B44D0AD9AF4@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <875C12B8-1E71-4808-AD3E-1B44D0AD9AF4@yahoo.com> X-Rspamd-Queue-Id: 49w8Zc4DRgz47vj X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [3.59 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.39)[0.389]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.54)[0.537]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.77)[0.769]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 01:11:21 -0000 On Sun, Jun 28, 2020 at 05:21:33PM -0700, Mark Millard wrote: > On 2020-Jun-28, at 12:50, bob prohaska wrote: > > > I'll update OS sources and try again, if somebody can tell me > > how to capture more useful information I'll try that. > > Do you have your system set up to allow it to > dump to the swap/paging space for panics and > then to put a copy in the /var/crash/ area during > the next boot? Konstantin B. was asking for > information from such a dump. > Ahh, that might be a little beyond my skill level.... The system is basically default -current, no kernel options. In fact, I'm no longer sure where to put them when using buildkernel. > Note: A dump can be requested at the db> prompt > by typing a "dump" command at the prompt, if you > have set up to have a dump target identified, > usually a swap/paging partition. If it works, the > next boot would take some time putting material > into /var/crash. > I'll try next time it happens. Looks like the system defaults turn on dumpdev and savecore. > Do you have devel/gdb installed? It supplies a > /usr/local/bin/kgdb for looking at such vmcore.* > files. Not yet. > > It is important that the kernel debug information > still match the vmcore as I understand, even if > that means needing to boot a different, > sufficiently-working kernel that does not match the > debug information in order to get the /var/crash > materials in place and to inspect them. > > I'm not sure you could do as Konstantin requested > based on a non-debug kernel build done the usual > way, even with debug information present. > One step at a time..... 8-) > Are you using a non-debug kernel? A debug-kernel? The embarrasing truth is I don't know. Whatever is default in -current for the Pi3. > You might need to try reproducing with a debug > kernel. (But that likely will make builds > take longer.) > Any sense of how much longer? A chromium build, when it worked, took a week. Thanks for writing! bob prohaska