Date: Wed, 01 Aug 2007 14:00:35 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Bruce Evans <brde@optusnet.com.au> Cc: "Chauncey N. Menefee" <cmenefee@prism-grp.com>, 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: <86odhrlb18.fsf@ds4.des.no> In-Reply-To: <20070731072434.F5028@besplex.bde.org> (Bruce Evans's message of "Tue\, 31 Jul 2007 08\:26\:21 %2B1000 \(EST\)") References: <200707301716.l6UHG3eD020378@www.freebsd.org> <20070731072434.F5028@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86odhrlb18.fsf>