From owner-freebsd-net@FreeBSD.ORG Sun Aug 9 12:50:27 2009 Return-Path: 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 79F411065675 for ; Sun, 9 Aug 2009 12:50:27 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 69D878FC2B for ; Sun, 9 Aug 2009 12:50:27 +0000 (UTC) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n79CoRHJ056654 for ; Sun, 9 Aug 2009 12:50:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n79CoRTv056645; Sun, 9 Aug 2009 12:50:27 GMT (envelope-from gnats) Date: Sun, 9 Aug 2009 12:50:27 GMT Message-Id: <200908091250.n79CoRTv056645@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Reko Turja Cc: Subject: Re: kern/129352: [xl] [patch] xl0 watchdog timeout X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Reko Turja List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Aug 2009 12:50:28 -0000 The following reply was made to PR kern/129352; it has been noted by GNATS. From: Reko Turja To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/129352: [xl] [patch] xl0 watchdog timeout Date: Sun, 9 Aug 2009 14:56:44 +0300 (EEST) After running the patch from this PR for some days I still got some watchdog timeouts. As another approach, I'm trying the driver revision 1.4 from /src/sys/dev/xl/ (8.x sourcetree) which compiled clean on my system with sources updated as of today. My uname -a: FreeBSD xxx.org 7.2-STABLE FreeBSD 7.2-STABLE #10: Sun Aug 9 14:13:47 EEST 2009 root@xxx.org:/usr/obj/usr/src/sys/MORIA i386 The reason for trying 1.4 was the commit message: SVN rev 191345 on 2009-04-21 00:42:11Z by yongari To make it easy whether xl(4) missed Tx completion interrupt check number of queued packets in watchdog timeout handler. If there are no queued packets just print a informational message and return without resetting controller. Also fix to invoke correct Tx completion handler as 3C905B needs different handler. I will send a followup after testing the driver for a while - if it seems to work, is there any chance of backporting it for 7.x? -Reko