Date: Fri, 23 Feb 2007 10:09:54 +0200 From: Alexander Shikoff <minotaur@crete.org.ua> To: freebsd-stable@freebsd.org Subject: Re: Cannot obtain kernel dump in /var/crash Message-ID: <20070223080954.GA93664@crete.org.ua> In-Reply-To: <20070222162824.GA24305@icarus.home.lan> References: <20070222115644.GA55416@crete.org.ua> <20070222132224.GA14615@icarus.home.lan> <20070222141333.GA60026@crete.org.ua> <20070222162824.GA24305@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 22, 2007 at 08:28:25AM -0800, Jeremy Chadwick wrote: > On Thu, Feb 22, 2007 at 04:13:33PM +0200, Alexander Shikoff wrote: > > /etc/rc.d/dumpon creates symbolic link /dev/dumpdev. It's present in > > my /dev directory. I think a problem is somewhere deeply, probably > > with savecore(8). When a panic occurs I see in console process of > > dumping (size of RAM, number of pages, dump device etc.) and it's > > completely normal. > > Anything shown on the actual console? There's some error conditions > which emit messages via syslog() only (see lines ~278-286 of > src/sbin/savecore/savecore.c). > > Also, any chance of output from savecore -f -vv? There's some extra > debugging info which might come in handy (lines ~288 of > src/sbin/savecore/savecore.c). Checking for core dump on /dev/ad2s1b... ----> savecore -f -vv /var/crash /dev/ad2s1b unable to open bounds file, using 0 checking for kernel dump on device /dev/ad2s1b mediasize = 1073741824 sectorsize = 512 magic mismatch on last dump header on /dev/ad2s1b savecore: unable to force dump - bad magic savecore: no dumps found Feb 23 10:04:05 savecore: unable to force dump - bad magic -- Kind Regards, Alexander Shikoff minotaur@crete.org.ua Mob.: +380 67 946 31 49
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070223080954.GA93664>