From owner-freebsd-questions@FreeBSD.ORG Wed Mar 7 04:55:56 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 33C4516A401 for ; Wed, 7 Mar 2007 04:55:56 +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 1B6DC13C481 for ; Wed, 7 Mar 2007 04:55:56 +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 1HOoBv-000CgM-LJ for freebsd-questions@freebsd.org; Tue, 06 Mar 2007 21:55:55 -0700 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <17838240D9A5544AAA5FF95F8D52031601C59D59@ad-exh01.adhost.lan> References: <17838240D9A5544AAA5FF95F8D52031601C59D59@ad-exh01.adhost.lan> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4A2E499D-27D6-4676-B7A0-CA56B1CF6699@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Tue, 6 Mar 2007 21:55:54 -0700 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: Wed, 07 Mar 2007 04:55:56 -0000 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. If it starts to happen again I will try and log in to the console and do the netstat -i then... In the morning I will break out my powerbook and get the switch port assignments off a chart I have there so I can log in to the switch and check the port for errors. I have not swapped ports/cables on the switch this time around but have had the exact same symptoms on a server with the same HW that was using different cables and a different switch... I may swap cables but the machine is downtown and I am not so unless I cannot make progress I want to avoid going downtown :-) I may swap the mainboard if it happens again to see if it is HW. I have one or two spare mainboards of the same sort. Thanks! Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net