Bug #2290

mount_linprocfs panic: lockmgr: LK_RELEASE: no lock held

Added by thomas.nikolajsen almost 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:01/26/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

On current RELEASE_3_0, 26th Januar 2012,
mount_linprocfs panics.
After 'kldload linux' succeeds,
'mount /compat/linux/proc', using fstab line below,
results in immediate panic.

Core dump available on request.

- fstab
linproc /compat/linux/proc linprocfs rw

-
panic: lockmgr: LK_RELEASE: no lock held
-
(kgdb) bt
#0 _get_mycpu () at ./machine/thread.h:79
#1 md_dumpsys (di=0xc0b056e0)
at /usr/src/sys/platform/pc32/i386/dump_machdep.c:264
#2 0xc03831a8 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:925
#3 0xc03837be in boot (howto=<optimized out>)
at /usr/src/sys/kern/kern_shutdown.c:387
#4 0xc0383a27 in panic (fmt=0xc06b44d7 "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:831
#5 0xc018d8f2 in db_panic (addr=-1067261374, have_addr=0, count=-1,
modif=0xd01dc8d4 "") at /usr/src/sys/ddb/db_command.c:445
#6 0xc018dfbf in db_command (aux_cmd_tablep_end=0xc0740bc0,
aux_cmd_tablep=0xc0740ba4, cmd_table=<optimized out>,
last_cmdp=<optimized out>) at /usr/src/sys/ddb/db_command.c:401
#7 db_command_loop () at /usr/src/sys/ddb/db_command.c:467
#8 0xc0190b1e in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:71
#9 0xc062e5b5 in kdb_trap (type=3, code=0, regs=0xd01dc9f4)
at /usr/src/sys/platform/pc32/i386/db_interface.c:151
#10 0xc066053a in trap (frame=0xd01dc9f4)
at /usr/src/sys/platform/pc32/i386/trap.c:838
#11 0xc062faa7 in calltrap ()
at /usr/src/sys/platform/pc32/i386/exception.s:787
#12 0xc062e242 in breakpoint () at ./cpu/cpufunc.h:72
#13 Debugger (msg=0xc06ce5b6 "panic")
at /usr/src/sys/platform/pc32/i386/db_interface.c:333
#14 0xc0383a08 in panic (fmt=0xc0711fa8 "lockmgr: LK_RELEASE: no lock held")
at /usr/src/sys/kern/kern_shutdown.c:822
#15 0xc037551a in lockmgr (lkp=0xd0240af0, flags=6)
at /usr/src/sys/kern/kern_lock.c:500
#16 0xc03f8d2d in vn_unlock (vp=0xd0240a18)
at /usr/src/sys/kern/vfs_vnops.c:1020
#17 0xc03ecfbf in vput (vp=0xd0240a18) at /usr/src/sys/kern/vfs_lock.c:593
#18 0xc03e78e0 in nlookup (nd=0xd01dcc70)
at /usr/src/sys/kern/vfs_nlookup.c:733
#19 0xc03f270c in kern_statfs (nd=0xd01dcc70, buf=0xd01dcb70)
at /usr/src/sys/kern/vfs_syscalls.c:1087
#20 0xc03f2854 in sys_statfs (uap=0xd01dccf0)
at /usr/src/sys/kern/vfs_syscalls.c:1123
#21 0xc0660b0c in syscall2 (frame=0xd01dcd40)
at /usr/src/sys/platform/pc32/i386/trap.c:1328


Related issues

Blocks Bug #2286: 3.0 release catchall ticket Closed 01/22/2012

History

#1 Updated by vsrinivas almost 3 years ago

Take a look at bug 2298 and commit 7fba7344c423a5a1e66111bacb99788c6ef68fbe; this problem should have been dealt with?

#2 Updated by thomas.nikolajsen almost 3 years ago

  • Status changed from New to Closed

Yes, you are right, problem is solved, thank you.

Also available in: Atom PDF