Ryota Ozaki <ozak...@netbsd.org> writes: > One possible fix has been committed. > > Can you update the source code and try a new kernel?
Will do. Meanwhile, before I got around to building a kernel with debug options enabled, I had another hang. Got it into DDB successfully, but then I managed, while looking for a way to switch between CPUs (the man page is wrong in this respect), to get DDB to look at something it shouldn't have, so it just said "fatal pag", and that was that. I did get a backtrace of CPU 0, though, and it looked interesting: pool_catchup() pool_get() pool_cache_get_slow() pool_cache_get_paddr() m_get() m_gethdr() wm_add_rxbuf() wm_rxeof() wm_intr_legacy() intr_biglock_wrapper() Xintr_ioapic_level2() --- interrupt --- Xspllower() uvm_km_kmem_alloc() pool_page_alloc() pool_grow() pool_catchup() pool_get() pool_cache_get_slow() pool_cache_get_paddr() m_get() m_gethdr() tcp_output() tcp_send_wrapper() sosend() soo_write() dofilewrite() sys_write() syscall() --- syscall (number 4) --- -tih -- Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay
