Date: Sat, 14 Jan 2017 18:40:02 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Mark Johnston <markj@FreeBSD.org> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org> Subject: Re: stable/11 debugging kernel unable to produce crashdump Message-ID: <587A0E12.7070205@grosbein.net> In-Reply-To: <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com> References: <587928B3.2050607@grosbein.net> <20170113193726.GC77535@wkstn-mjohnston.west.isilon.com>
index | next in thread | previous in thread | raw e-mail
> I suspect that this is because we only stop the scheduler upon a panic > if SMP is configured. Can you retest with the patch below applied? > > Index: sys/kern/kern_shutdown.c > =================================================================== > --- sys/kern/kern_shutdown.c (revision 312082) > +++ sys/kern/kern_shutdown.c (working copy) > @@ -713,6 +713,7 @@ > CPU_CLR(PCPU_GET(cpuid), &other_cpus); > stop_cpus_hard(other_cpus); > } > +#endif > > /* > * Ensure that the scheduler is stopped while panicking, even if panic > @@ -719,7 +720,6 @@ > * has been entered from kdb. > */ > td->td_stopsched = 1; > -#endif > > bootopt = RB_AUTOBOOT; > newpanic = 0; > > Indeed, my router is uniprocessor system and your patch really solves the problem. Now kernel generates crashdump just fine in case of panic. Please commit the fix, thanks! Eugene Grosbeinhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?587A0E12.7070205>