>Number: 175365 >Category: kern >Synopsis: Freebsd 8.3-RELEASE kernel panics when Xorp tries to shutdown >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 17 04:50:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Daniel Spisak >Release: 8.3-RELEASE >Organization: Agiosat >Environment: FreeBSD dispatch-dev 8.3-RELEASE-p5 FreeBSD 8.3-RELEASE-p5 #0 r243618: Tue Nov 27 15:06:42 PST 2012 root@alix-dev1:/usr/obj/nanobsd.alix-prod-mcast-8.3-R/usr/src-RELENG-8.3/sys/ALIX1 i386 >Description: Myself and a colleague have been trying to use Xorp 1.8.6 (we pulled the source from the git repo about 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 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 >How-To-Repeat: Install Xorp 1.8.6 from Git repo source Run Xorp doing IGMP and PIM-SM Attempt to stop Xorp service or Attempt to reboot server Kernel Panic occurs >Fix: None that I am aware of. >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
