From owner-freebsd-current@FreeBSD.ORG Wed Feb 14 22:15:26 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C92C16A402 for ; Wed, 14 Feb 2007 22:15:26 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 74FDE13C471 for ; Wed, 14 Feb 2007 22:15:26 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id 020661AF38A for ; Wed, 14 Feb 2007 17:15:23 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by out1.internal (MEProxy); Wed, 14 Feb 2007 17:15:24 -0500 X-Sasl-enc: 0fdGUlfkeZ3+fC39Ap4W2GYLkBEzrxCt5EAAxjB4OV3Q 1171491322 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 37F122358D for ; Wed, 14 Feb 2007 17:15:21 -0500 (EST) Message-ID: <45D389FA.2010604@FreeBSD.org> Date: Wed, 14 Feb 2007 22:15:22 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.9 (X11/20070125) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <45C64E3A.7050407@kasimir.com> <45D37239.1020100@FreeBSD.org> In-Reply-To: <45D37239.1020100@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: panic: sbflush_internal: cc 4294966301 || mb 0 || mbcnt 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2007 22:15:26 -0000 I was able to reproduce this bug, although the circumstances under which I did it are weird. I have two NICs on the same box patched to the same Ethernet broadcast domain, but on interconnected switches with no spanning tree. If I stop VLAN_HWTAGGING on msk with a vlan interface attached, and then run ping -f to a local host via the network configured on fxp, it seems to trigger the problem. sb_cc is always 84 bytes, which is 20 bytes IPv4 header + 64 bytes of ICMP data, so it's definitely ping which is triggering the issue in my case. I haven't been able to get a clean dump yet as my 6.2-RELEASE userland doesn't seem to understand -CURRENT's minidumps. Hope this helps, BMS