From owner-freebsd-net@FreeBSD.ORG Thu Jan 17 23:11:13 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CBC6F152 for ; Thu, 17 Jan 2013 23:11:13 +0000 (UTC) (envelope-from dspisak@agiosat.net) Received: from mail-da0-f43.google.com (mail-da0-f43.google.com [209.85.210.43]) by mx1.freebsd.org (Postfix) with ESMTP id A1180B60 for ; Thu, 17 Jan 2013 23:11:13 +0000 (UTC) Received: by mail-da0-f43.google.com with SMTP id u36so1333491dak.30 for ; Thu, 17 Jan 2013 15:11:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:x-gm-message-state; bh=/ktkXC0xkO4mNWH2yPztB0xIQd2OoihFLVpWPe6Kf7w=; b=PLoBiVB6l0A+osM0JYFfrOwoS5N8kWcEZc6zlTB+2mJpgR1Aqq7ytt/Sh7bseDGkGj CJKV3tQq2OwqHTS+UFQL0M8Wuwms2uoihbSZx6WpGuP9xITgA3M3IjJKsf5qMJS8MnEg oic13n/7k2HiBSogT+hvx/dOuKDXnpUapBY9OssisBCyP9qYca0DynsRMlLrW07K9hbp gHYba5MPsFbfCav6CEldrexjGjf42avtvA8EAXt7O2/KpbYIxiE8YObbYZR9QCoRCXYM z7N7pqu8HBi6SorYBMsr31u9MvvUKOoz7FxUVuV1jfztal+nS3FjeuIic1JuvewfPl3L zcBA== X-Received: by 10.68.189.163 with SMTP id gj3mr18034854pbc.110.1358464267120; Thu, 17 Jan 2013 15:11:07 -0800 (PST) Received: from [192.168.123.154] (rrcs-74-62-198-26.west.biz.rr.com. [74.62.198.26]) by mx.google.com with ESMTPS id bv10sm2121365pab.14.2013.01.17.15.11.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Jan 2013 15:11:06 -0800 (PST) Message-ID: <50F88509.5040602@agiosat.net> Date: Thu, 17 Jan 2013 15:11:05 -0800 From: Daniel Spisak User-Agent: Postbox 3.0.6 (Windows/20121031) MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Freebsd 8.3-RELEASE kernel panics when Xorp-1.8.6 tries to shutdown References: <50F78416.8080901@agiosat.net> In-Reply-To: <50F78416.8080901@agiosat.net> X-Gm-Message-State: ALoCoQlTpxuZY/AhUZq5WYVAPK+gRjVLoRe6twAhPlwYqy/31OEsfeLqZWAD0GfzS46IsgB/l5kd Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 23:11:13 -0000 Is anyone that is familiar with the FreeBSD multicast networking code able to speak up here regarding these kernel panics? Thanks. > Daniel Spisak > Wednesday, January 16, 2013 8:54 PM > Hi there, I'm new to the list! > > Myself and a colleague have been trying to use Xorp 1.8.6 (we pulled > the source from the git repo about a two months ago) to handle > multicast routing over GRE tunnels for a rather convoluted scenario. > In the course of trying to get that setup working (which will be > another separate email to the list) we seem to be running into > behavior from Xorp that is causing kernel panics to happen on FreeBSD > 8.3-RELEASE. > > Currently, we are able to startup Xorp normally with no apparent > problems. However, as soon as we try to shutdown the Xorp service or > initiate a system reboot the system will kernel panic. We are running > Xorp on ALIX1.D single board computers. You can see more about the > hardware specs here: > > http://pcengines.ch/alix1d.htm > > I have created a file dump of some of the kernel panics along with > some kdbg backtraces for developers to take a look at (along with a > kernel.debug for our kernel build). If I am reading the backtraces > right, it looks like there might be an issue being caused by IGMP > somehow. Perhaps a mismatch between v2 and v3? > > http://www.mediafire.com/?ojxdc172mp7q6 > > I'm pretty new to Xorp and multicast so its possible I've missed > something here. I've gone ahead and used send-pr to submit the error > and you can find it here: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=175365 > > Output from fbsd for interfaces: > > dispatch-dev# ifconfig -a > vr0: flags=8a43 > metric 0 mtu 1500 > > options=8280b > ether 00:0d:b9:0e:32:d4 > inet XX.XX.XXX.XX netmask 0xfffffffc broadcast XX.XX.XXX.XX > inet 192.168.10.2 netmask 0xffffff00 broadcast 192.168.10.255 > inet 10.13.8.253 netmask 0xffffff80 broadcast 10.13.8.255 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet 127.0.0.1 netmask 0xff000000 > enc0: flags=0<> metric 0 mtu 1536 > pflog0: flags=0<> metric 0 mtu 33200 > gre0: flags=9010 metric 0 mtu 1476 > > If anyone has any input/insight as to what is causing the kernel > panics and how to fix it, that would be great. Thanks! > -- Daniel Spisak Network Engineer dspisak@agiosat.net