Date: Thu, 9 Jan 2020 09:23:14 -0800 From: bob prohaska <fbsd@www.zefox.net> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: panic: non-current pmap on RPI3 on CURRENT (GENERIC) #4 r356366 Message-ID: <20200109172314.GA20008@www.zefox.net> In-Reply-To: <20200109115123.GZ23031@kib.kiev.ua> References: <20200108235630.GA17485@www.zefox.net> <20200109115123.GZ23031@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 09, 2020 at 01:51:23PM +0200, Konstantin Belousov wrote: > > It would be useful to see both the curcpu pc_curpmap content, > and dump both *(struct pmap *)0xfffffd000385f5a0 and *pc_curpmap > from the vmcore. The machine is presently updating to r356529. If the panic recurs, and somebody can describe how to capture more useful information, I'd be pleased to do it. References to documentation are welcome, but, not being a programmer, my ability to understand it is limited. Thanks for reading! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200109172314.GA20008>