From nobody Mon Feb 12 18:02:41 2024
X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TYXTs5ndHz5BGhB;
	Mon, 12 Feb 2024 18:06:57 +0000 (UTC)
	(envelope-from warlock@phouka1.phouka.net)
Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116])
	(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 "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified))
	by mx1.freebsd.org (Postfix) with ESMTPS id 4TYXTs19T5z4bTQ;
	Mon, 12 Feb 2024 18:06:57 +0000 (UTC)
	(envelope-from warlock@phouka1.phouka.net)
Authentication-Results: mx1.freebsd.org;
	none
Received: from phouka1.phouka.net (localhost [127.0.0.1])
	by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 41CI2fWC028945
	(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO);
	Mon, 12 Feb 2024 10:02:41 -0800 (PST)
	(envelope-from warlock@phouka1.phouka.net)
Received: (from warlock@localhost)
	by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 41CI2fTM028944;
	Mon, 12 Feb 2024 10:02:41 -0800 (PST)
	(envelope-from warlock)
Date: Mon, 12 Feb 2024 10:02:41 -0800
From: John Kennedy <warlock@phouka.net>
To: John Baldwin <jhb@freebsd.org>
Cc: Michael Butler <imb@protected-networks.net>,
        Mark Millard <marklmi@yahoo.com>,
        FreeBSD ARM List <freebsd-arm@freebsd.org>,
        Current FreeBSD <freebsd-current@freebsd.org>,
        Warner Losh <imp@bsdimp.com>, Bakul Shah <bakul@iitbombay.org>
Subject: Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1
 "rman_manage_region: <pcib1 memory window> request" leads to panic
Message-ID: <ZcpdQQwxQ1Nplg7_@phouka1.phouka.net>
References: <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5.ref@yahoo.com>
 <76AB969F-5BC5-4116-8AF4-3ED2CABEBBA5@yahoo.com>
 <2FE8FA48-180B-4F0D-BCD8-F7F33053B0F7@iitbombay.org>
 <986D2CD6-6241-4EBE-8BD2-9821AB693BA7@yahoo.com>
 <b0416b04-68a1-4aa5-9e9c-4d8a82279ac8@protected-networks.net>
 <b060f465-57ef-47cf-9a4f-30f6f39fbf62@FreeBSD.org>
List-Id: Porting FreeBSD to ARM processors <freebsd-arm.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arm
List-Help: <mailto:freebsd-arm+help@freebsd.org>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Subscribe: <mailto:freebsd-arm+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arm+unsubscribe@freebsd.org>
Sender: owner-freebsd-arm@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b060f465-57ef-47cf-9a4f-30f6f39fbf62@FreeBSD.org>
X-Spamd-Result: default: False [-4.00 / 15.00];
	REPLY(-4.00)[];
	ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]
X-Rspamd-Queue-Id: 4TYXTs19T5z4bTQ
X-Spamd-Bar: ----
X-Rspamd-Pre-Result: action=no action;
	module=replies;
	Message is reply to one we originated

On Mon, Feb 12, 2024 at 09:36:46AM -0800, John Baldwin wrote:
> Without a stack trace it is pretty much impossible to debug a panic like this.
> Do you have KDB_TRACE enabled in your kernel config?  I'm also not sure how the
> PCI changes can result in a panic post-boot.  If you were going to have problems
> they would be during device attach, not after you are booted and running X.
> 
> Short of a stack trace, you can at least use lldb or gdb to lookup the source
> line associated with the faulting instruction pointer (as long as it isn't in
> a kernel module), e.g. for gdb you would use 'gdb /boot/kernel/kernel' and then
> 'l *<instruction pointer address>', e.g. from above: 'l *0xffffffff80acb962'

  I know on my RPI4 where I saw that, my USB keyboard was dead at that point
and I couldn't get a trace or continue along to get the crashdump.