Date: Wed, 5 May 2021 18:51:30 +0200 From: Michael Schmiedgen <schmiedgen@gmx.net> To: Mark Johnston <markj@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: page fault while in kernel mode - after upgrade from 12.2 to 13.0 Message-ID: <197967f8-9675-4342-7961-8c902a57f58d@gmx.net> In-Reply-To: <51a3abc5-76b9-df09-acbe-895b62ec87b3@gmx.net> References: <d7c3bfbd-2e54-c0f4-ec23-5dab08287ea3@gmx.net> <YJBS8YMZFkMtWPEu@nuc> <d37716a3-927d-b200-c805-b31d7b36383d@gmx.net> <YJGaUnWCPVXRC4NC@nuc> <51a3abc5-76b9-df09-acbe-895b62ec87b3@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.05.2021 18:35, Michael Schmiedgen wrote: > On 04.05.2021 21:02, Mark Johnston wrote: >> This looks like fairly random kernel memory corruption. Are you able to >> build an INVARIANTS kernel and test that? Assuming you're using 13.0, >> you'd grab the 13.0 sources, add "options INVARIANT_SUPPORT" and >> "options INVARIANTS" to the GENERIC kernel configuration in >> sys/amd64/conf, and do a "make buildkernel installkernel". > > Below some info with an INVARIANTS kernel. Please let me know if I can provide > further information. Thank you! > > > --- kgdb backtrace > > > (kgdb) backtrace > #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 > #1 doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:399 [...] FYI, I just triggered another panic with INVARIANTS and the backtrace looks like the one before. Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?197967f8-9675-4342-7961-8c902a57f58d>