> Well I FINALLY got one of my crashing CGI machines to drop into > the debugger, and the results were interesting. I'm not a DDB expert, but > I tried to get some relevant info. I think the following is the most > interesting: > > db> trace > zalloci(c02698c0,deb59e58,c01f24c3,dd196964,8752000) at zalloci+0x33 > get_pv_entry(dd196964,8752000,ffc21d48,0,deb59e90) at get_pv_entry+0x4a > pmap_insert_entry(dd196964,8752000,c08952d0,77cb000) at > pmap_insert_entry+0x1f > pmap_copy(dd196964,de0ec264,80c6000,1d7e000,80c6000) at pmap_copy+0x1a0 > vm_map_copy_entry(de0ec200,dd196900,dd31aac8,de780208) at > vm_map_copy_entry+0xdf > vmspace_fork(de0ec200,dd191840,dd191840,bfbfddbc,deb59f30) at > vmspace_fork+0x1d3 > vm_fork(de09f080,dd191840,14) at vm_fork+0x2f > fork1(de09f080,14,deb59f48,de09f080,9) at fork1+0x621 > fork(de09f080,deb59f80,805b36c,30,bfbfddbc) at fork+0x16 > syscall(bfbf002f,bfbf002f,bfbf002f,bfbfddbc,30) at syscall+0x19e > Xint0x80_syscall() at Xint0x80_syscall+0x31 > > The full output of what I got is available at > http://doug.simplenet.com/DDB1.txt. > If you have a crash dump, could you look at the 4 longwords starting at address 0xc02698c0? It seemed to be an accouting problem. Do you by any chance use any kld module? zalloc() calls from within a module do not lock the vm_zone data structure, which is fine for UP but dangerous for SMP. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
