From owner-freebsd-questions@FreeBSD.ORG Thu Mar 15 06:18:38 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88F7816A401 for ; Thu, 15 Mar 2007 06:18:38 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE5E13C44C for ; Thu, 15 Mar 2007 06:18:38 +0000 (UTC) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.51) id 1HRjIL-000998-MT for freebsd-questions@freebsd.org; Thu, 15 Mar 2007 00:18:37 -0600 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <4A2E499D-27D6-4676-B7A0-CA56B1CF6699@shire.net> References: <17838240D9A5544AAA5FF95F8D52031601C59D59@ad-exh01.adhost.lan> <4A2E499D-27D6-4676-B7A0-CA56B1CF6699@shire.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Thu, 15 Mar 2007 00:18:36 -0600 To: User Questions X-Mailer: Apple Mail (2.752.2) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Subject: Re: started getting repeated "bge0: PHY read timed out" messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2007 06:18:38 -0000 On Mar 6, 2007, at 9:55 PM, Chad Leigh -- Shire.Net LLC wrote: > > On Mar 6, 2007, at 5:08 PM, Michael K. Smith - Adhost wrote: > >> >> Have you looked at the output of 'netstat -i' to see if there are >> interface errors? Also, have you looked at the switch-side interface >> for errors, buffer problems, etc. (if that's possible)? Finally, >> have >> you swapped ports/cables on the switch? >> >> Regards, >> >> Mike > > > Hi Mike > > Right now it seems to be behaving. netstat -i shows no issues and > I have not had the problem recur again once I forced it from auto > negotiation which ended up at 1000tx full duplex to now be 100tx at > full duplex. I don't know if it is related to the problem or not > or is a coincidence that once I did that the problem has not > arisen. It happened about 3 times today before forcing the > connection to be 100tx. OK, this problem has not resurfaced since I hardwired the settings on the port to 100tx and full duplex. I have another system with the same board that got the same problem last Fall when I upgraded from 5.4 to 6.0 or 6.1. The problem this time was on 6.2. I have another one of these boards running on a system with 5.4 without issue at gigabit speed. It appears that something happened in the bge driver from 5.x to 6.x at gigabit speeds, at least with some of the supported chipsets. Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net