From owner-svn-src-all@FreeBSD.ORG Mon Nov 23 23:32:57 2009 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE162106566B for ; Mon, 23 Nov 2009 23:32:57 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 740FB8FC12 for ; Mon, 23 Nov 2009 23:32:57 +0000 (UTC) Received: from [192.168.1.38] (S0106005004e13421.vs.shawcable.net [70.71.167.197]) (authenticated bits=0) by sippysoft.com (8.14.3/8.14.3) with ESMTP id nANN3tGL022587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Nov 2009 15:03:57 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <4B0B14D5.3090903@FreeBSD.org> Date: Mon, 23 Nov 2009 15:03:49 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Joerg Sonnenberger References: <200911222050.nAMKoRYh029141@svn.freebsd.org> <20091123010511.GA14572@britannica.bec.de> In-Reply-To: <20091123010511.GA14572@britannica.bec.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: svn-src-all@FreeBSD.org Subject: Re: svn commit: r199670 - head/sys/dev/bge X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 23:32:57 -0000 Joerg Sonnenberger wrote: > On Sun, Nov 22, 2009 at 08:50:27PM +0000, Pyun YongHyeon wrote: >> Log: >> Fix two long standing bugs on bge(4). Most pre BCM5755 controllers >> have a DMA bug when buffer address crosses a multiple of the 4GB >> boundary(e.g. 4GB, 8GB, 12GB etc). > > Does this only affect transfers that *cross* a 4GB boundary or does it > also affect transfers that *end* at a 4GB boundary? E.g. if the mbuf > cluster starts at 0xffffff00 with size 0x100 -- will the DMA engine > stall happen or not? What about bce(4) driver? Could it be affected too? We've seen some periodic lookups with the bce machine under the load (7.2-release, 5708C). Installing the add-on intel pro-based card into the same machine resolved the issue for us. -Maxim