Date: Thu, 2 Aug 2007 06:44:18 -0600 From: "Chauncey Menefee" <cmenefee@prism-grp.com> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, "Bruce Evans" <brde@optusnet.com.au> Cc: freebsd-gnats-submit@freebsd.org, freebsd-i386@freebsd.org Subject: RE: i386/115054: NTP errors out on startup but restart of NTP fixes problem Message-ID: <9F5E73873BB02C49B8A450D673B536D7019ABF77@PMMX01.prismgroup.int> References: <200707301716.l6UHG3eD020378@www.freebsd.org><20070731072434.F5028@besplex.bde.org> <86odhrlb18.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
The link speed is hardcoded to 100 Mbps full duplex at the switch.=20 We'll try Bruce idea on Monday. Chauncey N. Menefee NOC Technician PRISM Technologies Cell phone: 209.712.8736 24 Hour NOC Support: 1-505-314-7865 -----Original Message----- From: Dag-Erling Sm=F8rgrav [mailto:des@des.no] Sent: Wed 8/1/2007 6:00 AM To: Bruce Evans Cc: Chauncey Menefee; freebsd-gnats-submit@freebsd.org; = freebsd-i386@freebsd.org Subject: Re: i386/115054: NTP errors out on startup but restart of NTP = fixes problem =20 Bruce Evans <brde@optusnet.com.au> writes: > Several versions of FreeBSD have annoying behaviouor for network > startup, involving the network not actually being up when ifconfig > returns and subsequent different mishandling of this by various > utilities. [...] > This problem seems to get worse with each release of FreeBSD and/or > with newer NICs. I never noticed fxp or even ed or rl NICs. Now it > is barely noticeable with fxp and very noticeable with sk, bge and em > NICs. I have never seen this with any of the cards I've used (xl, fxp, rl, re, sis, bge, sk, msk and probably others, in no particular order). Perhaps there is a hardware issue involved? Does the problem occur if you hardcode the link speed instead of relying on autonegotiation? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F5E73873BB02C49B8A450D673B536D7019ABF77>