Subject: kern/11160: panic: lockmgr: no context
To: None <gnats-bugs@gnats.netbsd.org>
From: None <deberg@xennahtron.com>
List: netbsd-bugs
Date: 10/07/2000 16:23:10
>Number: 11160
>Category: kern
>Synopsis: panic: lockmgr: no context
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Oct 07 16:23:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: matt
>Release: 1.5F
>Organization:
>Environment:
System: NetBSD chamomile.xennahtron.com 1.5F NetBSD 1.5F (CHAMOMILE) #1: Sun Sep 24 18:18:30 EDT 2000 root@chamomile.xennahtron.com:/src/netbsd/src/sys/arch/i386/compile/CHAMOMILE i386
>Description:
on next68k, while doing a make build:
panic: lockmgr: no context
db> t (hand copied)
_panic(1c31e, beefd000, beefd000, 2, 2100) + 60
_lockmgr(11452c, 1, 0) + 72
_uvm_fault(114528, beefd000, 0, 1) + c4
_trap(8, 505, beefdeb9) + 562
_tprintf_open(3836af8) + 14
_nfs_msg(...) + e
_nfs_timer(0) + fe
_softclock
_hardclock
_clock_intr
_isrdispatch_autovec
_intrhand_autovec
_mi_switch
_ltsleep
_sched_sync
_proc_trampoline
>How-To-Repeat:
>Fix:
i dunno. i guess it was never anticipated that tprintf_open would trap
from the softclock context.
>Release-Note:
>Audit-Trail:
>Unformatted: