Date: Wed, 16 Jun 2004 14:12:27 +1000 From: John Birrell <jb@cimlogic.com.au> To: Michael Roberts <tpen0010@hotmail.com> Cc: freebsd-current@freebsd.org Subject: Re: bfe0 with/without acpi -- "watchdog timeout" error Message-ID: <20040616041227.GJ15577@freebsd3.cimlogic.com.au> In-Reply-To: <Sea1-F659WFHpwSPE0u0004e968@hotmail.com> References: <Sea1-F659WFHpwSPE0u0004e968@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040616041227.GJ15577>