From owner-freebsd-net@FreeBSD.ORG  Tue Sep 29 06:16:31 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F0E201065692;
	Tue, 29 Sep 2009 06:16:31 +0000 (UTC) (envelope-from bms@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id C720E8FC08;
	Tue, 29 Sep 2009 06:16:31 +0000 (UTC)
Received: from freefall.freebsd.org (bms@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8T6GVoQ052801;
	Tue, 29 Sep 2009 06:16:31 GMT
	(envelope-from bms@freefall.freebsd.org)
Received: (from bms@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8T6GVme052795;
	Tue, 29 Sep 2009 06:16:31 GMT (envelope-from bms)
Date: Tue, 29 Sep 2009 06:16:31 GMT
Message-Id: <200909290616.n8T6GVme052795@freefall.freebsd.org>
To: universite@ukr.net, bms@FreeBSD.org, freebsd-net@FreeBSD.org
From: bms@FreeBSD.org
Cc: 
Subject: Re: kern/138666: [multicast] [panic] not working multicast through
	igmpproxy
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: Tue, 29 Sep 2009 06:16:32 -0000

Synopsis: [multicast] [panic] not working multicast through igmpproxy

State-Changed-From-To: open->feedback
State-Changed-By: bms
State-Changed-When: Tue 29 Sep 2009 06:15:33 UTC
State-Changed-Why: 
Based on backtrace, it's difficult to say what the problem could be.
ENOTIME to attempt reproducing the condition. Initial testing around
the time of the last commits to ip_mroute.c didn't expose any problems,
have you checked out the memory on the affected machine?

http://www.freebsd.org/cgi/query-pr.cgi?pr=138666