kern/45177: DIAGNOSTIC panic: arch/x86/x86/pmap.c:3215: KASSERT(uvm_page_locked_p(pg)) fails

[kardel%pip.acrys.com@localhost]

>Number:         45177
>Category:       kern
>Synopsis:       DIAGNOSTIC panic: arch/x86/x86/pmap.c:3215: 
>KASSERT(uvm_page_locked_p(pg)) fails
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 24 18:20:00 +0000 2011
>Originator:     Frank Kardel
>Release:        NetBSD 5.99.55
>Organization:
        
>Environment:
        
        
System: NetBSD pip.kardel.name 5.99.55 NetBSD 5.99.55 (PIPGEN) #43: Mon Jun 13 
09:18:54 MEST 2011 
kardel%pip.kardel.name@localhost:/fs/raid1a/src/NetBSD/tc-merge/obj.amd64/sys/arch/amd64/compile/PIPGEN
 amd64
Architecture: amd64
Machine: amd64
>Description:
        With 5.99.55 amd64 I started to get KASSERT(uvm_page_locked_p(pg) 
panics from postgresql running in i386 emulation mode. 5.99.54 didn't seen to 
sensible.

        Hand copied stack trace:
        panic in arch/x86/x86/pmap.c:3215 ($NetBSD: pmap.c,v 1.127 2011/07/05 
14:07:12 yamt Exp $)
        pmap_remove_pte
        pmap_remove
        genfs_directio
        ffs_write

        postgresql opens files with O_DIRECT. 
>How-To-Repeat:
        run "ANALYZE VERBOSE" on a large table with postgresql(i386) and amd64 
5.99.55. Sometimes the panic also happens at startup of postgresql.

>Fix:

>Unformatted: