kern/46053: Diagnostic assertion failed in uvm/uvm_vnode.c

[Hauke Fath <hf%spg.tu-darmstadt.de@localhost>]

>Number:         46053
>Category:       kern
>Synopsis:       Diagnostic assertion failed in uvm/uvm_vnode.c
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 19 12:55:02 +0000 2012
>Originator:     Hauke Fath
>Release:        NetBSD 6.0_BETA
>Organization:
        Technische Universitaet Darmstadt
        
>Environment:
        
        
System: NetBSD 6.0_BETA 
Architecture: i386
Machine: i386
>Description:

        I dumped the partitions of a fileserver to re-organise the HW
        RAID layout. The restored system (major difference: The data
        partition was 'newfs -O2'ed with 64k/8k instead of the previous
        32k/4k) boots single-user, but during multi-user boot panics
        both with netbsd-5 and netbsd-6 kernels with

        (netbsd-5)

[...]
Starting mountd.
Starting nfsd.
Starting statd.
Starting lockd.
panic: kernel diagnostic assertion "oldsize != VSIZENOTSET || pgend > oldsize" 
failed: file "/public/netbsd-5/sys/uvm/uvm_vnode.c", line 353
Begin traceback...
uvm_fault(0xc0568d80, 0xfffff000, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c0381731 cs 8 eflags 10246 cr2 ffffffff ilevel 0
panic: trap
Faulted in mid-traceback; aborting...
dumping to dev 19,1 offset 8
dump amr0: bad status (not active; 0x0416)
127 amr0: bad status (not active; 0x0416)
amr0: bad status (not active; 0x0412)
[...]
56 amr0: bad status (not active; 0x0416)
error 35


amr0: bad status (not active; 0x040)
rebooting...


[...]
Starting mountd.
Starting nfsd.
Starting statd.
Starting lockd.
Starting virecover.
Starting local daemons:.
Starting lpd.
Updating motd.
panic: kernel diagnostic assertion "oldsize != VSIZENOTSET || pgend > oldsize" 
failed: file "/public/netbsd-5/sys/uvm/uvm_vnode.c", line 353
Begin traceback...
WARNING: SPL NOT LOWERED ON SYSCALL EXIT
uvm_fault(0xc056ff40, 0xfffff000, 1) -> 0xe
WARNING: SPL NOT LOWERED ON TRAP EXIT
fatal page faultWARNING: SPL NOT LOWERED ON TRAP EXIT
 in supervisor mode
WARNING: SPL NOT LOWERED ON TRAP EXIT
trap type 6 code 0 eip c0381a61 cs 8 eflags 10246 cr2 ffffffff ilevel 0
WARNING: SPL NOT LOWERED ON TRAP EXIT
panic: WARNING: SPL NOT LOWERED ON TRAP EXIT
trapWARNING: SPL NOT LOWERED ON SYSCALL EXIT

WARNING: SPL NOT LOWERED ON TRAP EXIT
Faulted in mid-traceback; aborting...WARNING: SPL NOT LOWERED ON TRAP EXIT

dumping to dev 19,1 offset 8
WARNING: SPL NOT LOWERED ON TRAP EXIT
dump WARNING: SPL NOT LOWERED ON TRAP EXIT
[...]
rebooting...


        (netbsd-6)

[...]
Starting mountd.
Starting nfsd.
Starting statd.
panic: keStarting lockd.rnel diagnostic assertion "oldsize != VSIZENOTSET || 
pgend > oldsize" failed: file "/public/netbsd-6/sys/uvm/uvm_vnode.c", line 350 
cpu1: Begin traceback...
kern_assert(c0b6a714,c0b6a8c5,c0c1374c,c0c13670,15e,dd31588c,dd31581c,c0851268,dd3157f8,ffffffff)
 at netbsd:kern_assert+0x23
uvm_vnp_setsize(c7c9cb0c,fbf3f850,fb46fb2b,dd31588c,0,0,dd315890,c08b4e36,3f,c0cd7df8)
 at netbsd:uvm_vnp_setsize+0x1bf
ffs_vget(c4fc2000,2627a00,0,dd3158d0,0,0,dd3158fc,0,3f,c4c97000) at 
netbsd:ffs_vget+0x427
ufs_fhtovp(c4fc2000,dd315908,dd315aa0,7,c483b744,c,2627a00,23dcc3a0,c4fc2000,dd315aa0)
 at netbsd:ufs_fhtovp+0x31
ffs_fhtovp(c4fc2000,dd315ab8,dd315aa0,c7cb3d40,c0ccbdc0,c0ccbdc0,dd31596c,c7cb9f18,dd315aa0,0)
 at netbsd:ffs_fhtovp+0x6c
VFS_FHTOVP(c4fc2000,dd315ab8,dd315aa0,dd315978,dd31597c,0,dd3159cc,c08a6521,c0ccbdc0,100)
 at netbsd:VFS_FHTOVP+0x27
nfsrv_fhtovp(dd315aac,1,dd315aa0,c7c82300,c45ed000,c4ddde00,dd315a98,0,0,0) at 
netbsd:nfsrv_fhtovp+0x99
nfsrv_getattr(c7cb9f18,c45ed000,c7cb3d40,dd315b68,ffffffff,c7bff2a8,dd315c8c,c7cb3d40,c7cb5e24,2)
 at netbsd:nfsrv_getattr+0x18c
nfssvc_nfsd(dd315bf0,b87ff928,c7cb3d40,0,0,0,0,c07b0571,0,0) at 
netbsd:nfssvc_nfsd+0x19f
sys_nfssvc(c7cb3d40,dd315cf4,dd315d1c,0,c7c79a80,0,0,c7cb2800,cb50e000,c7cb3d40)
 at netbsd:sys_nfssvc+0x237

syscall(dd315d48,b3,ab,1f,1f,0,b8600000,b87ff9ac,b87ff928,4) at 
netbsd:syscall+0xad
cpu1: End traceback...

dumping to dev 19,1 offset 8
dump amr0: bad status (not active; 0x0416)
amr0: bad status (not active; 0x0412)
amr0: bad status (not active; 0x0416)
amr0: bad status (not active; 0x0416)
amr0: bad status (not active; 0x0412)
135 earrmror0 :3 b5
ad
 s
tatus (not active; 0x040)
rebooting...


        The complaints from the amr(4) RAID controller driver may or
        may not be from a confused kernel. The machine worked fine
        before with uptimes 150+ d.

        Forcing a full fsck on all the volumes did not make a
        difference.

        Disabling the nfs server and its helper daemons appears 
        to avoid the panic, but leaves the NFS server useless.
 
        I am aware of PR 43287, however the hardware and kernel
        versions are reasonably different so I didn't want to
        hijack 43287.


>How-To-Repeat:

        See above; the panic is repeatable on my machine, although I
        do not understand what change made it behave that way.
        
>Fix:
        No idea.

>Unformatted: