Date: Wed, 14 Mar 2007 23:48:23 -0700 From: "Michael K. Smith - Adhost" <mksmith@adhost.com> To: "Chad Leigh -- Shire.Net LLC" <chad@shire.net>, "User Questions" <freebsd-questions@freebsd.org> Subject: RE: started getting repeated "bge0: PHY read timed out" messages Message-ID: <17838240D9A5544AAA5FF95F8D52031601C5A39E@ad-exh01.adhost.lan> In-Reply-To: <EADB3847-B5F5-49E4-9636-B30D58210F18@shire.net> References: <C0F3B817-FA3D-416C-B99B-971F51BA5E93@shire.net><E4469298-827B-433A-A537-8423A520A110@shire.net><17838240D9A5544AAA5FF95F8D52031601C59D59@ad-exh01.adhost.lan><4A2E499D-27D6-4676-B7A0-CA56B1CF6699@shire.net> <EADB3847-B5F5-49E4-9636-B30D58210F18@shire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Chad: -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Chad Leigh -- Shire.Net LLC Sent: Wednesday, March 14, 2007 11:19 PM To: User Questions Subject: Re: started getting repeated "bge0: PHY read timed out" messages 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, =20 >> 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 =20 > I have not had the problem recur again once I forced it from auto =20 > negotiation which ended up at 1000tx full duplex to now be 100tx at =20 > full duplex. I don't know if it is related to the problem or not =20 > or is a coincidence that once I did that the problem has not =20 > arisen. It happened about 3 times today before forcing the =20 > connection to be 100tx. OK, this problem has not resurfaced since I hardwired the settings on =20 the port to 100tx and full duplex. I have another system with the same board that got the same problem =20 last Fall when I upgraded from 5.4 to 6.0 or 6.1. The problem this =20 time was on 6.2. I have another one of these boards running on a =20 system with 5.4 without issue at gigabit speed. It appears that =20 something happened in the bge driver from 5.x to 6.x at gigabit =20 speeds, at least with some of the supported chipsets. Chad ---- Have you considered hard-setting the speed/duplex to 1000/Full instead of 100/Full? There may be some issues in the autonegotiation happening between switch and server. We used to see some of this early on in inter-vendor GigE connections; perhaps the switch vendor and the FreeBSD devels are reading the standards differently. Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17838240D9A5544AAA5FF95F8D52031601C5A39E>