On Sat, Jan 14, 2017 at 06:40:02PM +0700, Eugene Grosbein wrote: > > > 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!
Thanks, committed as r312199. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
