bfe0 with/without acpi -- "watchdog timeout" error
tpen0010 at hotmail.com
Wed Jun 16 13:36:16 GMT 2004
ahh, excellent, it works now. that's interesting -- i synced up with cvsup
about 4-5 days ago and did a make buildworld, and that's when the problems
started. i just used cvsup to sync with just the /usr/src/sys directory,
rebuilt my kernel, and all is ok now, it appears.
thanks for your speedy help.
>From: John Birrell <jb at cimlogic.com.au>
>To: Michael Roberts <tpen0010 at hotmail.com>
>CC: freebsd-current at freebsd.org
>Subject: Re: bfe0 with/without acpi -- "watchdog timeout" error
>Date: Wed, 16 Jun 2004 14:12:27 +1000
>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
> > when i boot the system with acpi enabled, the bfe0 ethernet device loads
> > 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
> > with acpi.. but for me, disabling acpi is what works. with acpi
> > bfe0 does not reset, and i can use the interface just fine (sic i am
> > 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.
MSN Toolbar provides one-click access to Hotmail from any Web page FREE
More information about the freebsd-current