The following reply was made to PR kern/32927; it has been noted by GNATS.

From: Andreas Wrede <andreas@planix.com>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Cc: 
Subject: Re: kern/32927: KASSERT(pmap->pm_obj.uo_npages == 0) failed on x86 3.99.13
Date: Thu, 25 May 2006 09:16:18 -0400

 I too can report this panic on a 3.0_STABLE production system, as of  
 Feb 18:
 
 panic: kernel diagnostic assertion "pmap->pm_obj.uo_npages == 0"  
 failed: file "/u1/netbsd-3.0/src/sys/arch/i386/i386/pmap.c", line 1816
 Begin traceback...
 __main(c06392f2,c069f8c0,718,c064dfd9,1c29d000) at netbsd:__main
 pmap_destroy(d0379e00,0,d12671ac,202,c0320ca5) at netbsd:pmap_destroy 
 +0xbf5
 pmap_load(c0320bed,cf303f2c,bfbfec58,4,cf303f5c) at netbsd:pmap_load 
 +0x125
 copyout(d1387234,cf303f64,cf303f5c,0,c1aa7000) at netbsd:copyout+0xe
 syscall_plain() at netbsd:syscall_plain+0x18f
 --- syscall (number 7) ---
 0xbdb2ae9f:               			[Thu May 25 03:28:40 2006]
 End traceback...				[Thu May 25 03:28:40 2006]
 syncing disks... arp_drain: locked; punting	[Thu May 25 04:06:59 2006]
 arp_drain: locked; punting                	[Thu May 25 04:06:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:06:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:11:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:11:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:11:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:11:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:21:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:21:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:51:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:51:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:51:59 2006]
 arp_drain: locked; punting			[Thu May 25 04:51:59 2006]
 arp_drain: locked; punting			[Thu May 25 05:26:59 2006]
 
 The times-tamps in [] were added by conserver. No more messages  
 follow for 3 hours. Breaking into the debugger:
 
 db> bt
 cpu_Debugger(0,c07481e0,0,800,c1b0a000) at netbsd:cpu_Debugger+0x4
 comintr(c1aa6a00,0,10,c1aa0030,10) at netbsd:comintr+0x6c1
 Xintr_ioapic_edge3() at netbsd:Xintr_ioapic_edge3+0x97
 --- interrupt ---
 ltsleep(ce5b8f40,11,c064549a,0,c06dbe38) at netbsd:ltsleep+0x422
 drain_output(ce5b8f1c,1,0,282,0) at netbsd:drain_output+0x60
 softdep_fsync_mountdev(ce5b8f1c,0,cf303cc8,c02d4b1e,cebee4a4) at  
 netbsd:softdep_fsync_mountdev+0x4f
 ffs_full_fsync(cf303d70,c1c7c000,cf303d68,c02d46bc,cf303d80) at  
 netbsd:ffs_full_fsync+0x35e
 ffs_fsync(cf303d70,10002,ce5b8f1c,c03704c4,c0571b20) at  
 netbsd:ffs_fsync+0x4c
 VOP_FSYNC(ce5b8f1c,cd3a06e4,0,0,0) at netbsd:VOP_FSYNC+0x4c
 ffs_sync(c1f37000,2,cd3a06e4,d02d17fc,cf2f64ac) at netbsd:ffs_sync+0xb4
 sys_sync(d1387234,0,0,78079cd8,100) at netbsd:sys_sync+0xb6
 vfs_shutdown(c06c8f20,0,cf303e88,c0342190,100) at netbsd:vfs_shutdown 
 +0x64
 cpu_reboot(100,0,7fffffff,cebeadc0,c06e5884) at netbsd:cpu_reboot+0x15f
 panic(c06c8f20,c06392f2,c064dfd9,c069f8c0,718) at netbsd:panic+0x108
 __main(c06392f2,c069f8c0,718,c064dfd9,1c29d000) at netbsd:__main
 pmap_destroy(d0379e00,0,d12671ac,202,c0320ca5) at netbsd:pmap_destroy 
 +0xbf
 pmap_load(c0320bed,cf303f2c,bfbfec58,4,cf303f5c) at netbsd:pmap_load 
 +0x125
 copyout(d1387234,cf303f64,cf303f5c,0,c1aa7000) at netbsd:copyout+0xe
 syscall_plain() at netbsd:syscall_plain+0x18f
 --- syscall (number 7) ---
 0xbdb2ae9f:
 db> sync
 
 dumping to dev 18,1 offset 1051455
 dump device bad
 
 
 rebooting...
 
 After that, the machine is locked up and requires a hard reset, so  
 there is no core dump.
 
 -- 
      aew