From owner-freebsd-net@FreeBSD.ORG Tue Feb 19 14:00:59 2008 Return-Path: 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 0AB1F16A469 for ; Tue, 19 Feb 2008 14:00:59 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id D1C7813C458 for ; Tue, 19 Feb 2008 14:00:58 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 490B38BDE9; Tue, 19 Feb 2008 09:00:58 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 19 Feb 2008 09:00:58 -0500 X-Sasl-enc: gdoCzOSXu/+aK0E7YuOpV5Jb2QSayKkzEpMoPHT/l5Ub 1203429657 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 3C37DDCBE; Tue, 19 Feb 2008 09:00:57 -0500 (EST) Message-ID: <47BAE118.2040508@FreeBSD.org> Date: Tue, 19 Feb 2008 14:00:56 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.9 (X11/20080207) MIME-Version: 1.0 To: Rob Watt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: panic in 6.3-RELEASE when multi-cast client exits X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2008 14:00:59 -0000 Rob Watt wrote: > Hi. > > We recently upgraded some of our machines to 6.3-RELEASE and we have been > plagued by repeatable panics when our multi-cast client applications exit. > Our machines have Intel X5365 processors, LSI MegaSAS 1064R cards, and Intel > Pro 1000 MF nic cards (although we have seen this problem with the onboard > Intel copper nics as well). We have seen this panic with machines that have > Tyan boards as well as Super Micro. I have seen a few postings that seem to > refer to related panics, and bug > http://www.freebsd.org/cgi/query-pr.cgi?pr=116077 contains a patch that > seems like it should address the problem, but our patched system still > panics. I have attached the output from 3 of the dumps/backtraces. Dump #1 > is probably the most useful. I am happy to provide more info if necessary. > Some folk reported that they didn't see this problem occur with the code in 7.x, which jibes as I rewrote some of the logic in that branch. It's been nearly a year since I last had time to look at anything related to this. My understanding is that 7.0 is getting closer to release status so you may wish to try reproducing the problem there. The human resource situation hasn't changed much on my end, though I am getting closer to having time to finishing IGMPv3 (it's needed for other stuff in the future). I haven't been able to reproduce the bug in the PR, which makes suggesting other courses of action difficult. cheers BMS