From owner-freebsd-net@FreeBSD.ORG  Mon Oct 25 19:19:58 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 384EC10656C6;
	Mon, 25 Oct 2010 19:19:58 +0000 (UTC)
	(envelope-from yongari@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 28EA88FC26;
	Mon, 25 Oct 2010 19:19:58 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o9PJJwEF003972;
	Mon, 25 Oct 2010 19:19:58 GMT
	(envelope-from yongari@freefall.freebsd.org)
Received: (from yongari@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9PJJvEX003968;
	Mon, 25 Oct 2010 19:19:57 GMT (envelope-from yongari)
Date: Mon, 25 Oct 2010 19:19:57 GMT
Message-Id: <201010251919.o9PJJvEX003968@freefall.freebsd.org>
To: junk@fromru.con, yongari@FreeBSD.org, freebsd-net@FreeBSD.org,
	yongari@FreeBSD.org
From: yongari@FreeBSD.org
Cc: 
Subject: Re: kern/150257: [msk] watchdog timeout
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:19:58 -0000

Synopsis: [msk] watchdog timeout

State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Mon Oct 25 19:17:29 UTC 2010
State-Changed-Why: 
I also have a DGE-560T but I can't reproduce this issue on my box.
Because you said disabling MSI fixed the issue I vaguely guess it
could be a silicon bug which controller sometimes looses Tx
completion interrupts or could be trggered by inappropriately
programmed event timer for the controller. It seems Yukon II
controllers are very sensitive to internal timer values so it can
also trigger the issue. I don't have permanent solution for these
issues but you can try the patch at the following URL.
http://people.freebsd.org/~yongari/msk/msk.watchdog.diff

It does not fix the issue but it will show watchdog timeout message
and tries to recover from that ranther than completely resetting
controller. If all goes ok, it sometimes shows watchdog timeouts but
it wouldn't reset controller such that you can treat the watchdog
timeouts as information message.


Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Mon Oct 25 19:17:29 UTC 2010
Responsible-Changed-Why: 
Grab.

http://www.freebsd.org/cgi/query-pr.cgi?pr=150257