>>>>> On Sat, 11 Feb 2006 02:14:11 -0500, >>>>> Kris Kennaway <[EMAIL PROTECTED]> said:
>> >> Sorry, not really (we've not got a test environment to reproduce it). >> >> But from a quick review of nd6.c, there seems to be one thing that is >> >> obviously wrong. The possible bug has been there since rev. 1.19 >> >> committed in April 2002. We've been probably just lucky so far... >> >> >> >> Could you try the patch attached below? We'll probably also need to >> >> apply this fix to 4.X and 5.X. >> >> > The patch did not fix the panic. >> >> Hmm, but this time the point where the panic happened should be >> different. Can you identify where it was? > I reduced the hw.physmem size and was able to get a dump: > (kgdb) frame 10 > #10 0xffffffff80333a86 in nd6_timer (ignored_arg=0xffffffff8059ab60) at > ../../../netinet6/nd6.c:585 > 585 ia6->ia6_flags |= IN6_IFF_DEPRECATED; Are you sure you applied the patch? In the 'patched' version of nd6.c, line 585 is blank, so at least it doesn't match the above backtrace. To make it very clear, I've put a copy of 'before' and 'after' the patch to nd6.c at: http://www.jinmei.org/nd6.c.orig and http://www.jinmei.org/nd6.c respectively. It seems you are still using nd6.c.orig, whose line 585 sets the IN6_IFF_DEPRECATED flag. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. [EMAIL PROTECTED] _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
