From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 00:02:17 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63DAE1065672 for ; Tue, 12 Oct 2010 00:02:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 1ECDD8FC17 for ; Tue, 12 Oct 2010 00:02:17 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id o9C02GMF001595; Mon, 11 Oct 2010 17:02:16 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id o9C02G6r001594; Mon, 11 Oct 2010 17:02:16 -0700 (PDT) (envelope-from sgk) Date: Mon, 11 Oct 2010 17:02:16 -0700 From: Steve Kargl To: Pyun YongHyeon Message-ID: <20101012000216.GA1554@troutmask.apl.washington.edu> References: <20101011225331.GA2829@troutmask.apl.washington.edu> <20101011231604.GI4607@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101011231604.GI4607@michelle.cdnetworks.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: recent bge(4) changes causing problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2010 00:02:17 -0000 On Mon, Oct 11, 2010 at 04:16:04PM -0700, Pyun YongHyeon wrote: > On Mon, Oct 11, 2010 at 03:53:31PM -0700, Steve Kargl wrote: > > > > In the time that it's taken me to compose this message > > the timeout has fire again. > > > > 15:47:07 kernel: bge0: watchdog timeout -- resetting > > 15:47:07 kernel: bge0: link state changed to DOWN > > 15:47:07 kernel: Limiting icmp unreach response from 439 to 200 packets/sec > > 15:47:08 kernel: Limiting icmp unreach response from 330 to 200 packets/sec > > 15:47:11 kernel: bge0: link state changed to UP > > 15:47:12 kernel: Limiting icmp unreach response from 214 to 200 packets/sec > > 15:47:13 kernel: Limiting icmp unreach response from 202 to 200 packets/sec > > 15:47:14 kernel: Limiting icmp unreach response from 238 to 200 packets/sec > > 15:49:42 kernel: bge0: link state changed to DOWN > > 15:49:44 kernel: bge0: link state changed to UP > > > > I not seen these icmp unreach response messages. > > > > The icmp unreach has nothing to do with bge(4). Check whether a > server that listens on an UDP port is still alive on your box. > What worries me is bge(4) watchdog timeouts. It looks like your > controller is BCM5704. I also have bge(4) regression report from > marius on sparc64. He said r213945 seemed to cause the issue and > I'm working on the issue. Could you also try the attached patch? The patch did not help. In fact, the icmp (which may be a side effect of the bge0 device wedging) has become much worse. SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad6s1a bge1: link state changed to UP bge0: link state changed to UP Limiting icmp unreach response from 3433 to 200 packets/sec Limiting icmp unreach response from 2017 to 200 packets/sec Limiting icmp unreach response from 2017 to 200 packets/sec Limiting icmp unreach response from 2049 to 200 packets/sec bge0: watchdog timeout -- resetting bge0: link state changed to DOWN Limiting icmp unreach response from 1962 to 200 packets/sec Limiting icmp unreach response from 2174 to 200 packets/sec Limiting icmp unreach response from 2180 to 200 packets/sec Limiting icmp unreach response from 2163 to 200 packets/sec bge0: link state changed to UP (removing 50 or so icmp messages). I don't know if the following helps, but thought I would include it here. troutmask:sgk[204] ping hpc PING hpc.apl.washington.edu (10.208.78.111): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available -- Steve