From owner-freebsd-isp@FreeBSD.ORG  Mon May 26 04:00:03 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E02F437B401; Mon, 26 May 2003 04:00:03 -0700 (PDT)
Received: from mail.cvt.dk (funnyitworkedlasttime.cvt.dk [130.225.95.154])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id EC36443F93; Mon, 26 May 2003 04:00:02 -0700 (PDT)
	(envelope-from cp@cvt.dk)
Received: from cvt.dk (cp.cvt.dk [130.225.95.152])
	by mail.cvt.dk (Postfix) with ESMTP
	id 8D8CFF38EA; Mon, 26 May 2003 13:00:00 +0200 (CEST)
Message-ID: <3ED1EFF1.C675DAD2@cvt.dk>
Date: Mon, 26 May 2003 12:44:01 +0200
From: Christoffer Pio <cp@cvt.dk>
Organization: Center for Videnteknologi
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Scott_Koh/Bluewave.BLUEWAVE@bluewave.com
References: <OFC43CC0E0.FEA9AD0C-ON48256D2D.00355250@bluewave.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-isp@freebsd.org
cc: freebsd-questions@freebsd.org
cc: Erwin Lansing <erwin@lansing.dk>
cc: owner-freebsd-questions@freebsd.org
Subject: Spooky em INTEL PRO 1000 driver?
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2003 11:00:04 -0000

Hello

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.

Please include my email in any replies.

Thanks
Christoffer
<cp@cvt.dk>