Date: Mon, 23 Jan 2012 17:07:43 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: new panic in cpu_reset() with WITNESS Message-ID: <20120123130743.GI16676@glebius.int.ru> In-Reply-To: <4F1D18A5.8010006@FreeBSD.org> References: <20120117110242.GD12760@glebius.int.ru> <20120120154158.GD16676@FreeBSD.org> <4F1ABFF3.9090305@FreeBSD.org> <20120122163539.GF16676@glebius.int.ru> <4F1D18A5.8010006@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 23, 2012 at 10:21:57AM +0200, Andriy Gapon wrote: A> > I can confirm that I can reboot succesfully with a new kernel A> > and kern.stop_scheduler_on_panic=0. A> A> This is very puzzling. You observation means that stop_scheduler_on_panic has A> an effect on the code outside the panic path. I reviewed the A> SCHEDULER_STOPPED() changes and I still can not see how that could be possible A> (modulo compiler bugs). A> A> Unfortunately, I also can not reproduce the problem here - without A> WITNESS_SKIPSPIN I am running into a panic[*] during boot. I suppose your patch (the one in other post) should help against this panic on boot. A> BTW, do you get any other LOR reports _before_ you do a reboot? I have some, but I don't think they are related. A> Can you try to change printfs in witness to db_printfs? Perhaps this will allow A> to get the details of the LOR in uart_cnputc. Maybe that will reveal some A> important additional details. Should I do s/printf/db_printf/ throughout entire subr_witness.c, or only in special places? A> Finally, can you try the patch from my other post? Yes, it works. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120123130743.GI16676>