:I made it happen again by doing the same installworld but this time I :caught it in the debugger. I'll leave the machine up for a while in case :someone has some idea of how to debug it. The stacktrace looks like this: : :#0 Debugger () at ../../alpha/alpha/db_interface.c:260 :#1 0xfffffc000036c2c0 in panic () at ../../kern/kern_shutdown.c:444 :#2 0xfffffc00004942fc in vm_page_alloc () at ../../vm/vm_page.c:1041 :#3 0xfffffc00003a1b54 in allocbuf () at ../../kern/vfs_bio.c:1791
The panic message should be printing the address of the vm_page_t that it caught. From the debugger, dump that vm_page_t with 'print'. print *0xADDRESS Do about 8 print's bumping the address by 4 ( in hex ) for each. It would be even better if we could figure out the contents and type of the underlying object. -Matt Matthew Dillon <dil...@backplane.com> :-- :Doug Rabson Mail: d...@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message