Date: Fri, 01 Jul 2005 16:32:38 -0400 From: Gary Mu1der <gmulder@infotechfl.com> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: panic in RELENG_5 UMA - two new stack traces Message-ID: <42C5A866.1010409@infotechfl.com> In-Reply-To: <20050701201308.GD59610@cell.sick.ru> References: <20050621090701.GB34406@cell.sick.ru> <20050621105154.GA36538@cell.sick.ru> <42B961B9.7A5856B3@freebsd.org> <20050623104230.GB61389@cell.sick.ru> <20050623141514.GD738@obiwan.tataz.chchile.org> <42BC5EE2.2020003@infotechfl.com> <20050627082958.GB97832@cell.sick.ru> <42C16BBF.4060107@infotechfl.com> <20050701085808.GD52023@cell.sick.ru> <42C58373.60008@infotechfl.com> <20050701201308.GD59610@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Gleb Smirnoff wrote: > G> I can reproduce the crash within 60 seconds of firing off 30+ ping/arp > G> -d scripts, all running in parallel. > G> > G> debug.mpsafenet=0 seems to have solved the problem. I'm running 100+ > G> instances of the above script and the system has been stable for over an > G> hour. > > Thanks! We definitely see that the bug is a race, not a broken logic. I am > almost sure, that you are experiencing the same bug as I described in > the beginning of the thread. > > Although there is no yet fix available for race between 'arp -d' and > outgoing packet, there is one for race between incoming ARP reply and > outgoing packet. We will probably commit it soon, after more review. Is this bug specific to only using "arp -d", or does it look like the "arp -d" tests identify a bug that might cause TCP/IP related crashes with other types of real-world network traffic. To rephrase: Does it look like fixing this bug may fix a lot of the network-related crashes a number of people have reported? Thanks, Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C5A866.1010409>