Date: Fri, 23 Mar 2007 10:11:40 -0400 From: "Simon Chang" <simonychang@gmail.com> To: "Rajkumar S" <rajkumars@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: No core dump after panic Message-ID: <8efc42630703230711l2b9bd09bpb46d169f044e0102@mail.gmail.com> In-Reply-To: <64de5c8b0703230345m265e8ieed0283b488a6e71@mail.gmail.com> References: <64de5c8b0703182321m5903c629ke480f039c02c3ee0@mail.gmail.com> <8efc42630703210526l17f7d4bbqb138b7bdcc1b5bc4@mail.gmail.com> <64de5c8b0703220000h6a5192ci6fe4e9d7eb8641f7@mail.gmail.com> <8efc42630703220500qba51f94md94bf5b018909103@mail.gmail.com> <64de5c8b0703220916r25eaf730yd3a6ca228e440c22@mail.gmail.com> <64de5c8b0703230345m265e8ieed0283b488a6e71@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. SC
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8efc42630703230711l2b9bd09bpb46d169f044e0102>