Date: Thu, 27 Sep 2007 21:16:47 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: Panic in rt_check Message-ID: <46FC019F.60900@FreeBSD.org> In-Reply-To: <9bbcef730709271208t74938933p704b554625f443ba@mail.gmail.com> References: <fddd8n$s82$1@sea.gmane.org> <46FBE818.3020800@FreeBSD.org> <9bbcef730709271054k5cbda605wcfd44adede05614f@mail.gmail.com> <46FBF101.6080402@FreeBSD.org> <9bbcef730709271208t74938933p704b554625f443ba@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras wrote: > On 27/09/2007, Kris Kennaway <kris@freebsd.org> wrote: > >> You will need to evaluate based on other evidence. e.g. if you've >> noticed other network flakiness on this machine to do with the gateway. > > No, I don't think there's anything like that. The panics began when I > upgraded to 7-current, the machine was stable under 6-stable. It might > be a coincidence or the new code is just more optimized and exposes > parallelism more. Yes, that is not really relevant, the same condition could have been occurring on your network prior to the upgrade. You may not notice if e.g. your switch is momentarily dropping carrier every now and then. >> Checking mtx_initialized won't help in that case because the race is >> still there. You'd need to check the places that can remove it and make >> sure they are all correctly locking the route first. > > I can only grep... OK, it likely needs more detailed investigation than that ;-) Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46FC019F.60900>