Date: Fri, 7 Oct 2022 18:28:14 -0400 From: Dennis Clarke <dclarke@blastwave.org> To: riscv@freebsd.org Subject: Re: panic: pmap_l2_to_l3: PA out of range, PA: 0x0 Message-ID: <55233680-630a-d800-3a06-9c13e9a7ba7d@blastwave.org> In-Reply-To: <13b80b07-1515-9aca-6490-a1b484c6aee4@freebsd.org> References: <cc66cdf0-04f8-913c-e2ec-4cea474a7995@blastwave.org> <13b80b07-1515-9aca-6490-a1b484c6aee4@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/7/22 18:08, Mitchell Horne wrote: > > > On 10/7/22 02:59, Dennis Clarke wrote: >> >> Saw this while trying to do buildworld .. which it was for days : >> . . . >> db> bt >> Tracing pid 18297 tid 100640 td 0xffffffc11af8a680 >> kdb_enter() at kdb_enter+0x48 >> vpanic() at vpanic+0x198 >> panic() at panic+0x2a >> pmap_remove_pages() at pmap_remove_pages+0x6c8 >> vmspace_exit() at vmspace_exit+0xd6 >> exit1() at exit1+0x4ac >> sys_exit() at sys_exit+0x10 >> do_trap_user() at do_trap_user+0x206 >> cpu_exception_handler_user() at cpu_exception_handler_user+0x72 >> --- exception 8, tval = 0 >> db> >> >> Anything worth looking at here or just pull the plug? >> >> > > Unlucky that you hit this, but the good news is the panic is known and > recently fixed. I committed a series of changes yesterday which address > the problem, ending with 1f9cc5ffc505. Well darn. Sometimes timing in life is everything. Thank you for letting me know. I will do a zpool scrub and then start over. Tomorrow maybe. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55233680-630a-d800-3a06-9c13e9a7ba7d>