No core dump after panic

Simon Chang simonychang at
Fri Mar 23 14:11:42 UTC 2007

Well, this means that, since your previous kernel panicked but was not
able to save a coredump, when you boot up from another kernel there is
simply nothing there for savecore to recover.  As a result savecore is
reporting that there is nothing to recover for you.

But that's the way to set it up.  And you can ignore the "unable to
open bounds file" message; it means that the bounds file wasn't there
but it created it for you automatically.


More information about the freebsd-questions mailing list