> 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 repr
ry for /usr/obj:
tmpfs /usr/objtmpfs size=2147483648,rw 0 0
Here's the panic on the console when it happened:
panic: lockmgr: locking against myself
cpuid = 2
KDB: enter: panic
[thread pid 61233 tid 100161 ]
Stopped at kdb_enter_why+0x3d:movq$0,0x394136(%rip
n of the kernel message buffer:
|> |> panic: lockmgr: locking against myself
|> |
|> | Is it 6.0-RELEASE and you have mounted NFS?
|>
|> Both, yes.
|
| I think 6.0-RELEASE-p1 should have fixed it... You may want to
| upgrade to RELENG_6_0 to get the patches.
I saw the commit abou
Hi, Mathieu,
On 12/20/05, Mathieu Arnold <[EMAIL PROTECTED]> wrote:
> +-le 20/12/2005 00:00 +0800, Xin LI a dit :
> | Hi,
> |
> | On 12/19/05, Mathieu Arnold <[EMAIL PROTECTED]> wrote:
> |> Unread portion of the kernel message buffer:
> |> panic: lockmgr: lock
+-le 20/12/2005 00:00 +0800, Xin LI a dit :
| Hi,
|
| On 12/19/05, Mathieu Arnold <[EMAIL PROTECTED]> wrote:
|> Unread portion of the kernel message buffer:
|> panic: lockmgr: locking against myself
|
| Is it 6.0-RELEASE and you have mounted NFS?
Both, yes.
--
Ma
Hi,
On 12/19/05, Mathieu Arnold <[EMAIL PROTECTED]> wrote:
> Unread portion of the kernel message buffer:
> panic: lockmgr: locking against myself
Is it 6.0-RELEASE and you have mounted NFS?
Cheers,
--
Xin LI <[EMAIL PROTECTED]> http
Hi
just got that today :
Unread portion of the kernel message buffer:
panic: lockmgr: locking against myself
cpuid = 0
Uptime: 2d21h29m5s
Dumping 510 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 510MB (130416 pages) 494 478 462 446 430 414 398 382 366 350 334
318 302 286 270 254
