Re: vm PANIC on RC1

Am Montag, 17. Oktober 2005 21:37 CEST schrieb Emanuel Strobl:
> Hello,
>
> I grabed this trace after my machine panics. This happens if I run links
> to swat on the local box over ssh forwarded X11
> II have ZERO_COPY_SOCKETS in my kernel and I'll try Andrew's patch, but
> I wanted to make sure this panic is seen by somebody who can read it ;)
[...]

Andrew Gallatins cow.diff hasn't helped, here's another trace, but removing 
ZERO_COPY_SOCKETS from kernel konfig seems to help. At least I couldn't 
trigger the panic without it.

Thanks,

-Harry

panic: vm_page_free: freeing wired page
KDB: enter: panic
[thread pid 557 tid 100103 ]
Stopped at      kdb_enter+0x30: leave
db> trace
Tracing pid 557 tid 100103 td 0xc19b4900
kdb_enter(c0742916,c07a7940,c07572aa,d1428b10,100) at kdb_enter+0x30
panic(c07572aa,1,c0756fae,3f1,125) at panic+0xd5
vm_page_free_toq(c1365ff0,40,c1365ff0,d1428b78,c06ad7af) at 
vm_page_free_toq+0xf7
vm_page_free(c1365ff0,0,c0756ae7,5eb,0) at vm_page_free+0x22
vm_object_backing_scan(c1b76c60,4,c0756ae7,633,12c) at 
vm_object_backing_scan+0x44f
vm_object_collapse(c1b76c60,0,c0756ae7,214,c1b3d948) at 
vm_object_collapse+0xfa
vm_object_deallocate(c1b3d948,0,c07561e3,89e,0) at 
vm_object_deallocate+0x36a
vm_map_entry_delete(c1b0a4b0,c1b7c2ec,846d000,d1428c38,c06a4de3) at 
vm_map_entry_delete+0x198
vm_map_delete(c1b0a4b0,0,bfc00000,c1b0a4b0,c1777780) at vm_map_delete+0x21c
vm_map_remove(c1b0a4b0,0,bfc00000,102,c17deb2c) at vm_map_remove+0x55
exit1(c19b4900,0,d1428d30,c06f8ba0,c19b4900) at exit1+0x6db
sys_exit(c19b4900,d1428d04,4,418,1) at sys_exit+0x1d
syscall(bfbf003b,3b,bfbf003b,8402a20,8408e40) at syscall+0x290
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x2848748f, esp = 
0xbfbfe9ec, ebp = 0xbfbfea08 ---