Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Mar 2007 23:16:22 -0600
From:      "illoai@gmail.com" <illoai@gmail.com>
To:        "Brian J. Conway" <bconway@clue4all.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Periodic xl watchdog timeouts on 6.2-RELEASE
Message-ID:  <d7195cff0703112216k41a12cf2nce5507d6ec1c522@mail.gmail.com>
In-Reply-To: <20070311221556.2d41802a.bconway@clue4all.net>
References:  <20070310105759.6980f90e.bconway@clue4all.net> <20070311221556.2d41802a.bconway@clue4all.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/03/07, Brian J. Conway <bconway@clue4all.net> wrote:
> On Sat, 10 Mar 2007 10:57:59 -0500
> "Brian J. Conway" <bconway@clue4all.net> wrote:
>
> > > I had exactly the same problem in my acpi-blacklisted motherboard. I
> > > disabled acpi and the errors vanished. In my case, this error was not
> > > related with NICs, but exclusively with the motherboard.
> >
> > Interesting.  I hadn't thought of that, but I am using ACPI now where I
> > was not on 4.x.  I'll give that a try next time it happens.  I would
> > have hoped the motherboard would be up to par (Intel D845GVSR with the
> > latest BIOS -
> > http://www.intel.com/products/motherboard/D845GVSR/index.htm), but maybe
> > not.  Thanks.
> >
> > (Sorry for the bad threading, I'm off list and copying off the web
> > archive.)
> >
> > Brian J. Conway
>
> No luck, got the first timeout shortly (25 min) after boot without ACPI,
> again while mostly idle and I'm not able to repeat it more than once a day
> or so:
>
> Mar 12 01:49:19 imogen kernel: xl0: watchdog timeout
> Mar 12 01:49:19 imogen kernel: xl0: link state changed to DOWN
> Mar 12 01:49:21 imogen kernel: xl0: link state changed to UP
>
> Any other ideas?  Original post, for reference:
> http://lists.freebsd.org/pipermail/freebsd-questions/2007-March/144227.html

My first suspicion was that your NIC is dying.
I had those basic symptoms some years ago
and within a few days was suffering unintended
reboots from kernel panics.  Replacing the NIC
solved it.

-- 
--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0703112216k41a12cf2nce5507d6ec1c522>