From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 00:11:11 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 452DF106564A for ; Tue, 12 Oct 2010 00:11:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 10B418FC17 for ; Tue, 12 Oct 2010 00:11:10 +0000 (UTC) Received: by pxi4 with SMTP id 4so447121pxi.13 for ; Mon, 11 Oct 2010 17:11:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=6fgY/kfIeW7yDGgTvNFlZmOtrOX99Mmv0sRj317LR80=; b=IRZ9pxWfBsO9lg7Ie/U6y0up+Zklwlgo9TbykMLjWzduEihXHkTq6DkI+hfSJ2SEok ExhrSya/0ZWhtk7jdYJAE8RFJQd+3adfI6tEsEOhikzcBgTTgYdQ6iUiEH5Oi8EYkAe1 4/HOCeCuOGfyAxhoWdskMKhEB3/oMgeksr3HE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Pzp2bBfKinnJm/7H1c2OYseejMYBpwDjKFOk/nMRAoCP6ZcGxEjWDOIkll9euMyxBU zym9J6HKtfyQXrvRkYyV3PokZlu5WxTxM6C+xBuk69YdyI1exf2I7gT4YHB6u+ivJCM0 MphYL4ILtIPsfg/jD6A53Ec8kYjwQsAn7h1oQ= Received: by 10.142.241.19 with SMTP id o19mr5722474wfh.20.1286842270456; Mon, 11 Oct 2010 17:11:10 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id w42sm23622wfh.3.2010.10.11.17.11.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 11 Oct 2010 17:11:09 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 11 Oct 2010 17:09:27 -0700 From: Pyun YongHyeon Date: Mon, 11 Oct 2010 17:09:27 -0700 To: Steve Kargl Message-ID: <20101012000927.GK4607@michelle.cdnetworks.com> References: <20101011225331.GA2829@troutmask.apl.washington.edu> <20101011231604.GI4607@michelle.cdnetworks.com> <20101012000216.GA1554@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101012000216.GA1554@troutmask.apl.washington.edu> 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 Reply-To: pyunyh@gmail.com 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:11:11 -0000 On Mon, Oct 11, 2010 at 05:02:16PM -0700, Steve Kargl wrote: > 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 > Would you show me the revision number of if_bge.c/if_bgereg.h? %cd /usr/src/sys/dev/bge %ident if_bge.c if_bgereg.h > > -- > Steve