From owner-freebsd-stable@FreeBSD.ORG Fri Mar 16 19:37:51 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9898616A402 for ; Fri, 16 Mar 2007 19:37:51 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5A30B13C44C for ; Fri, 16 Mar 2007 19:37:51 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l2GJbnh8006446; Fri, 16 Mar 2007 15:37:49 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Fri, 16 Mar 2007 15:37:45 -0400 User-Agent: KMail/1.6.2 References: <200703161430.42854.jkim@FreeBSD.org> <200703161848.l2GIm3H8043252@lava.sentex.ca> In-Reply-To: <200703161848.l2GIm3H8043252@lava.sentex.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200703161537.47359.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2852/Fri Mar 16 14:25:32 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: [PATCH] bge(4) patch for -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2007 19:37:51 -0000 On Friday 16 March 2007 02:46 pm, Mike Tancsa wrote: > At 02:30 PM 3/16/2007, Jung-uk Kim wrote: > >I have made bge(4) patch for -STABLE (sorry, not suitable for > >RELENG_6_2): > > > >http://people.freebsd.org/~jkim/bge_releng6.diff > > > >I received few success reports but I need wider testing because > >changes are too big and there are two many BCM57xx variants out > >there. If it breaks anything, please let me know. Especially, I > >want to hear more about IPMI/ASF mode support, i.e., if it doesn't > >work but setting hw.bge.allow_asf=0 in /boot/loader.conf fixes the > >problem, definitely I want to know. > > Hi, > What sort of problems does the patch fix ? I have a name > server that sees the odd watchdog reset. Do you think this would > address that problem ? Its not that frequent, but it does happen. > > eg > > Feb 17 17:59:28 auth2 kernel: bge0: watchdog timeout -- resetting > Feb 21 16:17:50 auth2 kernel: bge0: watchdog timeout -- resetting > Feb 28 11:13:11 auth2 kernel: bge0: watchdog timeout -- resetting > Mar 7 09:01:43 auth2 kernel: bge0: watchdog timeout -- resetting > Mar 10 10:21:12 auth2 kernel: bge0: watchdog timeout -- resetting > Mar 14 03:50:46 auth2 kernel: bge0: watchdog timeout -- resetting > > bge0: mem > 0xfe5f0000-0xfe5fffff irq 19 at device 0.0 on pci4 > miibus1: on bge0 > brgphy0: on miibus1 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > 1000baseTX, 1000baseTX-FDX, auto > bge0: Ethernet address: 00:e0:81:59:2b:06 It might fix your problem (i.e., we have some fixes for BCM5750 chipset family) but I am not so sure. Why don't you try it and tell me? ;-) Thanks, Jung-uk Kim