From owner-freebsd-questions@FreeBSD.ORG Mon Apr 19 13:18:03 2004 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 A36A516A4CE for ; Mon, 19 Apr 2004 13:18:03 -0700 (PDT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 692FB43D4C for ; Mon, 19 Apr 2004 13:18:03 -0700 (PDT) (envelope-from kdk@daleco.biz) Received: from daleco.biz ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 19 Apr 2004 15:18:51 -0500 Message-ID: <408433F8.3040702@daleco.biz> Date: Mon, 19 Apr 2004 15:18:00 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040406 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Henrik Zagerholm References: <40842D75.1000400@flowsolutions.se> In-Reply-To: <40842D75.1000400@flowsolutions.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Apr 2004 20:18:52.0187 (UTC) FILETIME=[8826E6B0:01C4264B] cc: freebsd-questions@freebsd.org Subject: Re: Networking problem! Watchdog -- Timeout X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 20:18:03 -0000 Henrik Zagerholm wrote: > Hi all! > Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC. > System detects it as em0 but I cant get it to work. I'm trying dhcp > and I have added the line: ifconfig_em0="DHCP" in rc.conf but I still > get this problem. > em0: Watchdog Timeout ---Resetting > > IF I disable ACPI it works perfectly so I think it's IRQ related or? Please note that I am not associated with the Project while you read this. I think that this is a bug with the em driver on the 5.X series. You did note that it's a "new technology" release and not "advertised" to be suitable for everybody, right? IIRC, there have been issues with both em(4) and ACPI on the -HEAD (CURRENT, 5.X) code for a while. Good programmers are giving lots of the time and energy, coding for free to get it working, but some things are tricky. You might run without ACPI for a while, switch NICs until the problem is fixed, or run 4.9 or 4.10 [which is due out Real Soon Now(tm)] instead of 5.2 .... Kevin Kinsey