Ivan and Kris, I will try to get a kernel trace -- it may not happen for awhile since I am not in the office and working remotely for awhile so it may not be easy to get a trace... but I will check.
It looks like the problem reported by that link, and some of the links from there though... Benjie On 9/24/07, Ivan Voras <[EMAIL PROTECTED]> wrote: > > Benjie Chen wrote: > > > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin > > c066c7b4 T _mtx_lock_spin > > c066c85c T _mtx_unlock_sleep > > > > So this could mean that independent stress tests will not result in > panic if > > there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html > > > > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
