lockmgr: thread 0xc385ebd0 unlocking unheld lock



Last night I was mounting a windows share with mount_smbfs and
browsing it via apache and I got the machine to panic twice. I was
tired and went to bed.
Today I can't replicate the panic but this always happens when I unmount:

lockmgr(c36cfb08,2006,c36cfb2c,c35251b0,d5926c00) at lockmgr+0x5c6
smb_co_put(c36cfb00,d5926c00,d5926c00,c35251b0,c3703280) at smb_co_put+0x46
smbfs_unmount(c33f6800,8000000,c35251b0,0,415) at smbfs_unmount+0x71
dounmount(c33f6800,8000000,c35251b0,c0733b28,0) at dounmount+0x286
unmount(c35251b0,d5926d04,c3527234,c,c35251b0) at unmount+0x1f6
syscall(3b,3b,3b,804a465,8201a51) at syscall+0x27e
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c205f, esp = 0xbfbfe54c, eb
p = 0xbfbfe5f8 ---

Another time, a different share:

lockmgr: thread 0xc385ebd0 unlocking unheld lock
KDB: stack backtrace:
kdb_backtrace(c06ca09c,c385ebd0) at kdb_backtrace+0x29
lockmgr(c36ed508,2006,c36ed52c,c385ebd0,dab78c00) at lockmgr+0x5c6
smb_co_put(c36ed500,dab78c00,dab78c00,c385ebd0,c3703280) at smb_co_put+0x46
smbfs_unmount(c33f5400,8000000,c385ebd0,0,415) at smbfs_unmount+0x71
dounmount(c33f5400,8000000,c385ebd0,c0733b28,0) at dounmount+0x286
unmount(c385ebd0,dab78d04,c385d000,c,c385ebd0) at unmount+0x1f6
syscall(3b,3b,3b,804a465,8201a51) at syscall+0x27e
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c205f, esp = 0xbfbfe53c, eb
p = 0xbfbfe5e8 ---

The machine is running CURRENT cvsuped last night with a kernel
compiled without a bunch of drivers. I can compile GENERIC if needed.

I'm trying to replicate the panic, and if I can I'll post a followup.
In the meantime if anyone can provide some insight on this or needs
more info I'm more than available.

--
Joao Barros
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: lockmgr: thread 0xc385ebd0 unlocking unheld lock
    ... browsing it via apache and I got the machine to panic twice. ... Today I can't replicate the panic but this always happens when I unmount: ... There is a PR about this - so you should add your traces there if it ...
    (freebsd-current)
  • Re: Replication failure after restore
    ... * This posting is provided "AS IS" with no warranties and confers no rights! ... "Hii Sing Chung" < I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)
  • Re: Replication failure after restore
    ... "Hii Sing Chung" < I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)
  • RE: Global Catalog Replication
    ... replicate changes to multi-valued attributes and won't replicate the entire ... available in a forest that is Windows Server 2003 Forest Functional Level. ... > The KCC is responsible for calculating a routing topology. ... > There is a Microsoft Press book titled "Active Directory for Microsoft ...
    (microsoft.public.windows.server.active_directory)
  • Replication failure after restore
    ... I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. ... The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. ... Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. ...
    (microsoft.public.win2000.active_directory)