From owner-freebsd-net@FreeBSD.ORG Thu Jan 17 04:54:58 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68DDBE2 for ; Thu, 17 Jan 2013 04:54:58 +0000 (UTC) (envelope-from dspisak@agiosat.net) Received: from mail-pb0-f53.google.com (mail-pb0-f53.google.com [209.85.160.53]) by mx1.freebsd.org (Postfix) with ESMTP id 46284320 for ; Thu, 17 Jan 2013 04:54:57 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id un1so513344pbc.40 for ; Wed, 16 Jan 2013 20:54:50 -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:cc :subject:content-type:x-gm-message-state; bh=LO8SwCHj8yjGop75/XEimvTx0OuF8zoZ+odSLk2FrQQ=; b=fMPDlzurKaNrbaLgdth/G2YsxW7qtqh8oqbgiO+pWmeuVtAqxUP/FWLB7aU/EXHPd3 94VyPwLq0RSISQMCu3G08Vsxbdy37JxMo4cJVVLZ8wJGVTLUJGjK1AFnVmqSfUCI50nB 4Xhvh8Atfq5nVTz+bCSL7c5fk9+4IxueZEdDCgXVqB+2RC0vywSI/enYyVuFEGtXBL0g DO0GzXjVM1J8iy6E7GWFxffqWECY7V4xKzDDYbBKkKVvnmM3lYdfE4yzfVkzwRMH8G+1 agafLmNsDUKwbeu9D3sNvA3y7wyKBHffgPLU7T7fPP2Rn0Z2llXm1PXwKjovaBDr+3Lh QiQg== X-Received: by 10.68.132.10 with SMTP id oq10mr9955204pbb.18.1358398490877; Wed, 16 Jan 2013 20:54:50 -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 is3sm329200pbc.6.2013.01.16.20.54.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jan 2013 20:54:50 -0800 (PST) Message-ID: <50F78416.8080901@agiosat.net> Date: Wed, 16 Jan 2013 20:54:46 -0800 From: Daniel Spisak User-Agent: Postbox 3.0.6 (Windows/20121031) MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Freebsd 8.3-RELEASE kernel panics when Xorp-1.8.6 tries to shutdown X-Gm-Message-State: ALoCoQlxqd4fikJ0h4PIX/BtJ8b7A9h68IDLSvOEc5OUlrHIm/ZmVolsd4ypbPKWj9btLHpYsKUN Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Keith Simonsen 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 04:54:58 -0000 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 Agiosat Government Services dspisak@agiosat.net