From owner-freebsd-isp@FreeBSD.ORG Mon May 26 15:07:53 2003 Return-Path: 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 A083237B404 for ; Mon, 26 May 2003 15:07:53 -0700 (PDT) Received: from mail.2goons.net (2goons.net [216.27.161.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F2343F93 for ; Mon, 26 May 2003 15:07:52 -0700 (PDT) (envelope-from mwilliams@2goons.net) Received: (qmail 64284 invoked by uid 89); 26 May 2003 16:41:10 -0000 Received: from unknown (HELO admin.2goons.net) (mwilliams@216.27.161.249) by 2goons.net with SMTP; 26 May 2003 16:41:10 -0000 MIME-Version: 1.0 X-Mailer: V-webmail 1.5.0 ( http://www.v-webmail.co.uk/ ) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <3ED1EFF1.C675DAD2@cvt.dk> References: <3ED1EFF1.C675DAD2@cvt.dk> Date: Mon, 26 May 2003 12:41:10 -0400 From: "MFW" To: Christoffer Pio , cc: freebsd-isp@freebsd.org cc: freebsd-questions@freebsd.org cc: Erwin Lansing cc: owner-freebsd-questions@freebsd.org Subject: Re: Spooky em INTEL PRO 1000 driver? X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: mwilliams@2goons.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 22:07:53 -0000 Christoffer, I have a similar problem with another driver. I am assuming that you have the em driver compiled in your Kernel (I think its in GENERIC in 4.8). Here is what I did to combat the similar problem. Take the ifconfig_em(x) and defaultrouter out of the rc.conf. Make a simple if_up.sh script in /usr/local/etc/rc.d to bring up your interfaces and bring up your default route. I run a sleep command in mine for 5 seconds to give other services time to load before I bring up the interfaces. Syslog should come up regardless of network services, unless you are doing remote syslog. Either way, the above worked for me. If that doesn't work, check to make sure you have the em driver compiled in your Kernel. Sounds like its trying to kldload the em driver, therefore making your services not start in the process (no network activity). If it is loading the module at boot up, then make the above script, but load the module at the top. Its all the same. Just an idea. Not saying it the right thing to do, but its one that worked for me. MFW Christoffer Pio wrote: > 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 > > _______________________________________________ > freebsd-isp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isp > To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" > _________________________________________________________ This mail sent using V-webmail - http://www.v-webmail.org