On Thu, May 26, 2011 at 05:54:24PM +0200, Joerg Wunsch wrote: J> As it turns out this might be related to something else that has been J> using that piece of memory before re(4) is activated, here are the J> boot messages for reference.
You can try to add 'options DEBUG_MEMGUARD' to your kernel config, and add the 'vm.memguard.desc=devbuf' to your /boot/loader.conf. This may help to find place where memory is tampered after free. -- Totus tuus, Glebius. _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
