From owner-freebsd-questions@FreeBSD.ORG Mon May 26 09:37:31 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 343BF37B401 for ; Mon, 26 May 2003 09:37:31 -0700 (PDT) Received: from devil.stderror.at (at00d01-adsl-194-118-044-149.nextranet.at [194.118.44.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63E5C43F3F for ; Mon, 26 May 2003 09:37:30 -0700 (PDT) (envelope-from pinhead@stderror.at) Received: by devil.stderror.at (Postfix, from userid 1000) id C6FFE15316; Mon, 26 May 2003 18:37:29 +0200 (CEST) Date: Mon, 26 May 2003 18:37:29 +0200 From: Toni Schmidbauer To: freebsd-questions@freebsd.org Message-ID: <20030526163729.GU60276@devil.stderror.at> Mail-Followup-To: freebsd-questions@freebsd.org References: <3ED1EFF1.C675DAD2@cvt.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Efge0/SQAHHP+Pr2" Content-Disposition: inline In-Reply-To: <3ED1EFF1.C675DAD2@cvt.dk> User-Agent: Mutt/1.4.1i Subject: Re: Spooky em INTEL PRO 1000 driver? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: toni@stderror.at List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 16:37:31 -0000 --Efge0/SQAHHP+Pr2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 26, 2003 at 12:44:01PM +0200, Christoffer Pio wrote: > I am experiencing some spookynes with FreeBSD 4.8 on the IBM > x345 2U machine; the x345 comes with two on-board INTEL 100/1000 mb nics > which uses the em driver. However, whenever I "up" one of the nics, > there is a slight delay of a few seconds before the command > completes, also the nic is not operating in up state yet, > appr. 30 seconds passes before traffic actually can pass > in/out .. It happens regardless if there is a cable attached > to the nic. I find this rather spooky. Has anyone using the > em driver experienced this? Other than being spooky it > causes a problem with the box in question, since syslogd and > other daemons times out at boot-up. could also be the switch config. ports on a cisco switch wait per default a view seconds before they activate the link. you have to disable spanning tree protocol on that port for an instant link. hth, toni --=20 Behandle die Menschen, als w=E4ren sie, was sie sein | toni at stderror dot= at sollten, und du wirst ihnen helfen, zu werden, was | Toni Schmidbauer sie sein k=F6nnen. - Johann Wolfgang von Goethe | --Efge0/SQAHHP+Pr2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+0kLJu/mjSj7RMocRArd6AJsHQnKjihZQOUVQSs0DID0So81mCQCghe7v VkowXgNREI3lTjoSqHkmp/M= =oQaG -----END PGP SIGNATURE----- --Efge0/SQAHHP+Pr2--