From owner-freebsd-net@FreeBSD.ORG Tue Aug 4 10:30:05 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 91A39106564A for ; Tue, 4 Aug 2009 10:30:05 +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 7FA908FC2B for ; Tue, 4 Aug 2009 10:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n74AU58M003745 for ; Tue, 4 Aug 2009 10:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n74AU5sj003737; Tue, 4 Aug 2009 10:30:05 GMT (envelope-from gnats) Date: Tue, 4 Aug 2009 10:30:05 GMT Message-Id: <200908041030.n74AU5sj003737@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: Tue, 04 Aug 2009 10:30:06 -0000 The following reply was made to PR kern/129352; it has been noted by GNATS. From: "Reko Turja" To: , Cc: Subject: Re: kern/129352: [xl] [patch] xl0 watchdog timeout Date: Tue, 4 Aug 2009 13:10:07 +0300 After updating my firewall box to 7.2-STABLE I started getting the=20 watchdog timeouts with the link state going down and returning back up=20 after couple of seconds on the xl interface. Some seeking from gnats=20 returned this bug report. I applied the patch succesfully on: src/sys/pci/if_xl.c,v 1.210.2.2 2008/04/23 21:28:29 and will give it a shot for some days in order to see if it breaks=20 something or if the watchdog timeouts still keep occurring. So far=20 rebooting after fresh kernel seems to be ok. =20