From owner-freebsd-stable@FreeBSD.ORG Sat Mar 17 13:35:22 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 BE27E16A403; Sat, 17 Mar 2007 13:35:22 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8AEF413C4D1; Sat, 17 Mar 2007 13:35:22 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id l2HDZLNi070960; Sat, 17 Mar 2007 09:35:21 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l2HDZLV8048080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Mar 2007 09:35:21 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200703171335.l2HDZLV8048080@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 17 Mar 2007 09:33:25 -0400 To: Jung-uk Kim , freebsd-stable@FreeBSD.org From: Mike Tancsa In-Reply-To: <200703161537.47359.jkim@FreeBSD.org> References: <200703161430.42854.jkim@FreeBSD.org> <200703161848.l2GIm3H8043252@lava.sentex.ca> <200703161537.47359.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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: Sat, 17 Mar 2007 13:35:22 -0000 At 03:37 PM 3/16/2007, Jung-uk Kim wrote: >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? ;-) Hi, I am running with your patch as applied to stable as of yesterday. Should know in about a week or two if the watchdog timeouts are gone post reboot it looks like 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 ---Mike