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> In-Reply-To: <b060f465-57ef-47cf-9a4f-30f6f39fbf62@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZcpdQQwxQ1Nplg7_>