From owner-freebsd-current@FreeBSD.ORG  Wed Jun 16 04:12:37 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3FF9216A4CE
	for <freebsd-current@freebsd.org>;
	Wed, 16 Jun 2004 04:12:37 +0000 (GMT)
Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au
	[218.214.20.121])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 659D943D5C
	for <freebsd-current@freebsd.org>;
	Wed, 16 Jun 2004 04:12:36 +0000 (GMT)
	(envelope-from jb@cimlogic.com.au)
Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102)
	id 194266AA57; Wed, 16 Jun 2004 14:12:28 +1000 (EST)
Date: Wed, 16 Jun 2004 14:12:27 +1000
From: John Birrell <jb@cimlogic.com.au>
To: Michael Roberts <tpen0010@hotmail.com>
Message-ID: <20040616041227.GJ15577@freebsd3.cimlogic.com.au>
References: <Sea1-F659WFHpwSPE0u0004e968@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Sea1-F659WFHpwSPE0u0004e968@hotmail.com>
User-Agent: Mutt/1.4.2.1i
cc: freebsd-current@freebsd.org
Subject: Re: bfe0 with/without acpi -- "watchdog timeout" error
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jun 2004 04:12:37 -0000

On Tue, Jun 15, 2004 at 07:20:56PM -0400, Michael Roberts wrote:
> i've run into a problem with -current, which wasn't there with 5.2 stable.  
> when i boot the system with acpi enabled, the bfe0 ethernet device loads up 
> and works for a short period of time, after which it gives the error 
> "watchdog timeout -- resetting".
> 
> after scanning the mailing lists, i saw that other people had had problems 
> with acpi.. but for me, disabling acpi is what works.  with acpi disabled, 
> bfe0 does not reset, and i can use the interface just fine (sic i am able 
> to send this message... :)
> 
> so -- what do i do to get both acpi and bfe0 running at the same time?  

The result of the discussion you've referred to was that one piece of the
ACPI code was backed out for the time being [ thanks to John Baldwin and
Nate Lawson for responding to the problems noted].

As of today, a cvsup of -current runs fine on my Dell 1150 which uses
bfe. I suggest you try updating - just keep a known good kernel around
just in case.

-- 
John Birrell