kern/45101: DIAGNOSTIC panic: uvm_amap.c:1459(amap_lookups()) an->an_lock == amap->am_lock

[kardel%pip.acrys.com@localhost]

>Number:         45101
>Category:       kern
>Synopsis:       DIAGNOSTIC panic: uvm_amap.c:1459(amap_lookups()) an->an_lock 
>== amap->am_lock
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 26 10:40:00 +0000 2011
>Originator:     Frank Kardel
>Release:        NetBSD 5.99.53-20110626060000
>Organization:
        
>Environment:
System: NetBSD pip.kardel.name 5.99.53 NetBSD 5.99.53 (PIPGEN) #1: Sun Jun 26 
08:30:38 CEST 2011 
kardel%pip.kardel.name@localhost:/fs/raid1a/src/NetBSD/cur/src/sys/arch/amd64/compile/obj/PIPGEN
 amd64
Architecture: x86_64
Machine: amd64
>Description:
        During pkgsrc/mk/bulk build I get regularly above panic. it is a normal 
bulk build
        (chroot environment built via null mounts).
        Machine AMD X6 1100T, 16GB memory, dmesg available on request.
        stack trace available when I copy it by hand next time.

        more issues seen during bulk builds:
                build.sh release has random lint SIGSEGVs (not repeatble at the 
same file)
                devel/fhist build will lock up in tstile
>How-To-Repeat:
        pick -current-20110626 (and also 1-2 weeks before) for amd64.
        set up bulk build (MAKE_JOBS=9)
        start - wait - panic in uvm_amap.c:1459
>Fix:
        disable diagnostic - probably will only delay the underlying problem

>Unformatted: