From owner-freebsd-current@FreeBSD.ORG Tue Oct 2 06:59:32 2012 Return-Path: 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 9A27D106566B; Tue, 2 Oct 2012 06:59:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 61B948FC0C; Tue, 2 Oct 2012 06:59:32 +0000 (UTC) Received: by padbi1 with SMTP id bi1so5639394pad.13 for ; Mon, 01 Oct 2012 23:59:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Ux9xK3D3Ywh43kb6aX4dIxDNhYII9fk5ncjeLhNWjNU=; b=WAomFShkD4WbHyTBaaHduWYDhaHMMpJVemJN9vBQdMFzRoFaEK8w10NRCF4D81oT23 UQn/IbsYuzejTtBzoZxnyKLRj9uOBywG5X43JQiezYcgjRrvMdLqwx3a4d7KunW6kbXO rRW7w3oEgTYkT6a9SBnDDR1rYg931ekSzlupW7IYZ+O5d21bPG/BAFvOx8VuHpWZGCFy +ySC826kvvQAZMCy+wzZYjz4TSFNSuie7qOhV7WxrfvUagNFOm7mn23bv02WVWPpR59E jpkQ+H61cNcrgRMEEzwZ168rlmwnFW5EWxV5yQPvsAk5XUMpeN6fE2KGM7h71qGrJtd7 OJmQ== Received: by 10.68.225.3 with SMTP id rg3mr2040844pbc.27.1349161172034; Mon, 01 Oct 2012 23:59:32 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id gv1sm473149pbc.38.2012.10.01.23.59.28 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 01 Oct 2012 23:59:31 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 02 Oct 2012 15:59:18 -0700 From: YongHyeon PYUN Date: Tue, 2 Oct 2012 15:59:18 -0700 To: sbruno@freebsd.org Message-ID: <20121002225918.GA15610@michelle.cdnetworks.com> References: <20120914212716.GB7612@michelle.cdnetworks.com> <1348073071.5775.4.camel@powernoodle.corp.yahoo.com> <1348790974.10543.16.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1348790974.10543.16.camel@powernoodle.corp.yahoo.com> User-Agent: Mutt/1.4.2.3i Cc: "freebsd-current@freebsd.org" Subject: Re: Call for bge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2012 06:59:32 -0000 On Thu, Sep 27, 2012 at 05:09:34PM -0700, Sean Bruno wrote: > On Wed, 2012-09-19 at 09:44 -0700, Sean Bruno wrote: > > On Fri, 2012-09-14 at 14:27 -0700, YongHyeon PYUN wrote: > > > All, > > > > > > There were lots of reports that stock bge(4) does not work on Dell > > > Rx20/HP DL 360 G8. With the help of Broadcom and BCM5719/BCM5720 > > > users I managed to address the issue but I had to touch very > > > sensitive part of driver. Before committing the change to tree I'd > > > like to know whether this change introduces regressions on old > > > bge(4) controllers. If you're bge(4) user, please try latest WIP > > > version at the following URL and let me know how it goes on your > > > box. I'm especially interested in whether there is any ASF/IPMI > > > regression on BCM570x/571x. > > > > > > http://people.freebsd.org/~yongari/bge/if_bge.c > > > http://people.freebsd.org/~yongari/bge/if_bgereg.h > > > http://people.freebsd.org/~yongari/bge/brgphy.c > > > > > We're starting to gather data and have a couple of machines (pciconf, > ifconfig, dmesg) here that may provide some insights. Everything seems > to be working at a cursory level. > > http://people.freebsd.org/~sbruno/new_bge/ Thanks for testing! Sean, do you have a box with BCM5703/5704/5714/5715 controller? If the answer is yes, would you give it spin on the box? Due to the reset sequence changes I'd like to know whether there are any regressions on these controllers. The reset sequence change will also affect BCM5906/5906M controller. I guess bge(4) didn't completely reset BCM5906 such that it may have resulted in RX CPU handing under device resume. The WIP version wouldn't completely solve resume issue but it would make one step forward to right direction. > > We have seen 2 instances of one or more of the HP machines failing and > dropping off the network. however, we don't have specifics yet. > > Sean