Date: Fri, 9 Jan 2009 12:18:56 +0100 From: Daniel Bond <db@danielbond.org> To: Omer Faruk Sen <omerfsen@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: kernel dump with 7.1-RELEASE Message-ID: <470C1D05-FD7B-4216-8598-36B6D886987B@danielbond.org> In-Reply-To: <75a268720901080805t3b85fa2bgf9b78abc1fb9a5c4@mail.gmail.com> References: <75a268720901080805t3b85fa2bgf9b78abc1fb9a5c4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I'm assuming you configured a a dump-device in rc.conf, but just in case, here are the options: db ~> grep dump /etc/defaults/rc.conf [p8@gonzales] dumpdev="AUTO" # Device to crashdump to (device name, AUTO, or NO). dumpdir="/var/crash" # Directory where crash dumps are to be stored savecore_flags="" # Used if dumpdev is enabled above, and present. using SWAP as the dumpdevice is the recommended way, as you sorta pointed out. More information can be found at: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html On Jan 8, 2009, at 5:05 PM, Omer Faruk Sen wrote: > Hi, > > I am having kernel dumps with FreeBSD 7.1 > > panic: semexit - semid not allocated > cpuid = 1 > Uptime : 8m22s > Cannot dump. No dump device defined > Sleeping thread (tid 100129, pid 1479) owns a non-sleepable lock > > > I know it is not clear and there were no swap space configured on this > server (which I will re-install with swap space) but can someone > enlighten me about this since I think this bug was also in FreeBSD 6.2 > and fixed in FreeBSD 6.3 > > Regards. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470C1D05-FD7B-4216-8598-36B6D886987B>