On Thu, 22 Jan 2009, Brett Lymn wrote:
How old are your sources? There was a fix that went in late last year to the routing code to stop it stomping random kernel memory - the bug would cause effects like you are seeing now. If your sources are up to date then you could try building a kernel with MALLOCLOG defined and see if there is anything that is consistently listed as a neighbour if/when you get a report of data modified on the malloc free list.
My sources are from about 1 week ago (netbsd-5 branch). How do I look at that log when the option's enabled in the kernel? - Hubert