>Number:         20149
>Category:       kern
>Synopsis:       switching with lock held warnings
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 01 03:36:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Martin Husemann
>Release:        NetBSD 1.6M
>Organization:
>Environment:
System: BetBSD sunny-weather.duskware.de 1.6M NetBSD 1.6M (SUNNY) #0: Sat Feb  1 10:46:11 CET 2003     martin@sunny-weather.duskware.de:/usr/src/sys/arch/sparc64/compile/SUNNY sparc64
Architecture: sparc64
Machine: sparc64
>Description:

On a sparc64 system, running current from last night with DEBUG/DIAGNOSTIC/
LOCKDEBUG enabled, I get a few messages like this once in a while when
stressing the machine:

switching with held simple_lock 0x287a2410 CPU 0 ../../../../uvm/uvm_amap_i.h:248
pool_get(PR_WAITOK) with held simple_lock 0x287a2410 CPU 0 ../../../../uvm/uvm_amap_i.h:248
pool_get(PR_WAITOK) with held simple_lock 0x287a2410 CPU 0 ../../../../uvm/uvm_amap_i.h:248
switching with held simple_lock 0x287a2410 CPU 0 ../../../../uvm/uvm_amap_i.h:248
switching with held simple_lock 0x287a2410 CPU 0 ../../../../uvm/uvm_amap_i.h:248

I have no idea if this is a pmap issue (thus port specific), so I put this
report into category kern for now.

>How-To-Repeat:

run build.sh -j 4 or worse.

>Fix:
n/a
>Release-Note:
>Audit-Trail:
>Unformatted: