From owner-freebsd-stable@FreeBSD.ORG  Mon Oct  5 20:53:59 2009
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 521E91065693
	for <freebsd-stable@freebsd.org>; Mon,  5 Oct 2009 20:53:59 +0000 (UTC)
	(envelope-from crapsh@monkeybrains.net)
Received: from ape.monkeybrains.net (mail.monkeybrains.net [208.69.40.9])
	by mx1.freebsd.org (Postfix) with ESMTP id 363818FC12
	for <freebsd-stable@freebsd.org>; Mon,  5 Oct 2009 20:53:59 +0000 (UTC)
Received: from [208.90.214.10] (rudy.york.monkeybrains.net [208.90.214.10])
	(authenticated bits=0)
	by ape.monkeybrains.net (8.14.3/8.14.1) with ESMTP id n95KrjiE049591
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 5 Oct 2009 13:53:45 -0700 (PDT)
	(envelope-from crapsh@monkeybrains.net)
Message-ID: <4ACA5D1E.10006@monkeybrains.net>
Date: Mon, 05 Oct 2009 13:54:54 -0700
From: Rudy <crapsh@monkeybrains.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Greg Byshenk <freebsd@byshenk.net>
References: <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com>	<4AC5198E.7030609@monkeybrains.net>	<4AC51B4C.7080905@monkeybrains.net>	<2a41acea0910011450v41590f3dn112f367f26faed2d@mail.gmail.com>	<4AC64835.3060107@monkeybrains.net>	<2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com>	<4AC66437.4040704@monkeybrains.net>	<6194E9BC-3A3D-4941-A777-88C7411905B0@danielbond.org>	<2a41acea0910050957x2d085e90w2ebea7f9eb87c3e4@mail.gmail.com>	<57F8F331-E823-4F88-BDD5-A8B95A3B4CB6@danielbond.org>
	<20091005200900.GE15606@core.byshenk.net>
In-Reply-To: <20091005200900.GE15606@core.byshenk.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.95.1 at pita.monkeybrains.net
X-Virus-Status: Clean
Cc: Daniel Bond <db@danielbond.org>,
	FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: em0 watchdog timeouts
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 20:53:59 -0000

> Finally, while doing some comparisons, I realized that the motherboard
> having the problem was _not_ the same as the others; it was similar, but
> not identical.

This is a good piece of info.  I can try swapping out the MB and see 
what happens.

I do want to add: thank you Jack for all your help and if does turn out 
to be the MB, then double thanks.  Viva Monday!   :)

What would be nice would be MORE info for a watchdog timeout... maybe a 
sysctl dev.watchdog.debug=1 or something where when a watchdog event 
happened --- for whatever driver --- a bunch of stats were dumped 
relating to the event.

Rudy