From owner-freebsd-net@FreeBSD.ORG  Thu Sep 27 19:16:47 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5E81416A468;
	Thu, 27 Sep 2007 19:16:47 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36])
	by mx1.freebsd.org (Postfix) with ESMTP id D885113C478;
	Thu, 27 Sep 2007 19:16:45 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <46FC019F.60900@FreeBSD.org>
Date: Thu, 27 Sep 2007 21:16:47 +0200
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Ivan Voras <ivoras@freebsd.org>
References: <fddd8n$s82$1@sea.gmane.org> <46FBE818.3020800@FreeBSD.org>	
	<9bbcef730709271054k5cbda605wcfd44adede05614f@mail.gmail.com>	
	<46FBF101.6080402@FreeBSD.org>
	<9bbcef730709271208t74938933p704b554625f443ba@mail.gmail.com>
In-Reply-To: <9bbcef730709271208t74938933p704b554625f443ba@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org
Subject: Re: Panic in rt_check
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Sep 2007 19:16:47 -0000

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