Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Apr 2009 22:01:27 -0400
From:      Josh Carroll <josh.carroll@gmail.com>
To:        stable <stable@freebsd.org>
Subject:   Re: panic: lockmgr: locking against myself on 7.2-BEA1 (and gmirror dumpdev not working)
Message-ID:  <8cb6106e0904071901l54f998bbt819c1530e2dfb7d0@mail.gmail.com>
In-Reply-To: <8cb6106e0904071651u79c5f8fdgf727c7118d9b6f73@mail.gmail.com>
References:  <8cb6106e0904071651u79c5f8fdgf727c7118d9b6f73@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> Unfortunately, as mentioned in the subject, I am unable to get a
> savecore. After show alllocks and bt, I ran "call doadump", which
> appeared to work fine. However, after rebooting, there was no savecore
> in /var/crash and running savecore against /dev/mirror/gm1s1b states:

I was able to reproduce the panic and this time, I booted single user
mode and I was able to manually call savecore to get
/var/crash/vmcore.0

So if there is any additional kgdb output needed, just say the word
and I can get it now.

Curious why /etc/rc.d/savecore didn't work on a normal reboot after
the dump, but that's probably a topic for a separate mail thread.

Thanks,
Josh



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8cb6106e0904071901l54f998bbt819c1530e2dfb7d0>