Date: Mon, 12 Feb 2024 12:21:27 -0800 From: Mark Millard <marklmi@yahoo.com> To: John Kennedy <warlock@phouka.net> Cc: John Baldwin <jhb@freebsd.org>, Michael Butler <imb@protected-networks.net>, 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: <5AEF0FB0-F8CB-46C9-B14F-0723136AA116@yahoo.com> In-Reply-To: <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> <ZcpdQQwxQ1Nplg7_@phouka1.phouka.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 12, 2024, at 10:02, John Kennedy <warlock@phouka.net> wrote:
> 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.
>>=20
>> 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'
>=20
> 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.
My serial console context still works at the panic.
But:
. . .
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x4c: str xzr, [x19, #1280]
db> dump
Cannot dump: no dump device specified.
db>=20
This is despite:
# grep dumpdev /boot/loader.conf
dumpdev=3D"/dev/da0p3"
and:
# gpart show -p
=3D> 40 468862048 da0 GPT (224G)
40 32728 - free - (16M)
32768 102400 da0p1 efi (50M)
135168 451809280 da0p2 freebsd-ufs (215G)
451944448 16916480 da0p3 freebsd-swap (8.1G)
468860928 1160 - free - (580K)
So, the panic may be before dumping is set up, at
least for USB3 media.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5AEF0FB0-F8CB-46C9-B14F-0723136AA116>