Date: Mon, 21 Jun 2021 09:24:08 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-3630-o7ABkZb7h6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256712 --- Comment #12 from Gary Jennejohn <gljennjohn@gmail.com> --- (In reply to Graham Perrin from comment #11) This reminds me of a kernel panic which I saw and reported on. I was asked to add INVARIANTS and DEBUG=3D-O0 to my kernel config file to g= et better backtraces. Since I already had makeoptions DEBUG=3D-g, I actually = added makeoptions DEBUG+=3D-O0 to get both -g and -O0 in the compiler flags. As one can see in your backtrace, parts of the kernel were optimized out. = The -O0 assures that no optimization is done. That will produce better backtrace. For INVARIANTS I added options INVARIANTS and options INVARIANT_SUPPORT. So, if you can easily reproduce the panic I recommend adding these to your kernel config file and then rerunning your test. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256712-3630-o7ABkZb7h6>