From owner-freebsd-stable@FreeBSD.ORG Wed Jun 16 00:05:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A934106566C; Wed, 16 Jun 2010 00:05:48 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF978FC13; Wed, 16 Jun 2010 00:05:48 +0000 (UTC) Received: by pvg2 with SMTP id 2so486348pvg.13 for ; Tue, 15 Jun 2010 17:05:47 -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=Hd3r7lqT3CXbz5uNg9akIDShltCmV2AvyvfYAEbCYt4=; b=AUa4x2681UEVxgeO9XDXHll2Z5mOto5l7pZ3MXcfeIeL/YWwC0+zg6FwSwMVRni+Tq Dam6Rrw9amlOjuIw3/l9YEuJzpuRqlK3ajHShaH1mA6P4MlpSzPfc+vc2pIESUM9g3ce Wc5B5ddm0BcyDMyKaUyFHr7mgkG2P01ORhczg= 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=G6OIFbCsRnMisvroS52zVeEhaCgaZcFqaVTs7RKq0ax0N2puUeSHDBy7oqgNoGFz2o DJQRR/9tCBNeoTLI9ReIseHH0PQ0z1nMXxNNmAM7V1SjbYy/59wmPfFD7u2ACtXITvNS tMCnHTq0flvPwnW2zkhlmJymsA1+MW5QPHp+g= Received: by 10.141.108.4 with SMTP id k4mr6370770rvm.111.1276646747583; Tue, 15 Jun 2010 17:05:47 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id o38sm6324760rvp.14.2010.06.15.17.05.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 15 Jun 2010 17:05:40 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 15 Jun 2010 17:05:00 -0700 From: Pyun YongHyeon Date: Tue, 15 Jun 2010 17:05:00 -0700 To: Artem Kim Message-ID: <20100616000500.GN4257@michelle.cdnetworks.com> References: <201006131934.11389.artem_kim@inbox.ru> <201006160257.01213.artem_kim@inbox.ru> <20100615232108.GM4257@michelle.cdnetworks.com> <201006160350.39502.artem_kim@inbox.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="DBIVS5p969aUjpLe" Content-Disposition: inline In-Reply-To: <201006160350.39502.artem_kim@inbox.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: Problems with bge (possibly related to r208993) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 00:05:48 -0000 --DBIVS5p969aUjpLe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jun 16, 2010 at 03:50:39AM +0400, Artem Kim wrote: > On Wednesday 16 June 2010 03:21:09 Pyun YongHyeon wrote: > > > Hmm, why you need link0 flag? The link0 flag is used to force the > > interface MASTER. Normally this configuration is automatically > > done during auto-negotiation such that one is configured as MASTER > > and the other is configured as SLAVE. If you manually configure > > this setting you should be very careful not to use the same > > configuration of MASTER/SLAVE of link partner. If you have to use > > link0 option, the link partner should be configured to use SLAVE. > > Normally you should always use auto-negotiation on 1000baseT unless > > link partner is severely broken to support NWAY. > > > > It seems link partner does not agree on resolved speed/duplex > > configuration of bge1. Check link partner's resolved link > > configuration. > > > > In any case, now I do not use the flag link0. > Now the master/slave is assigned through auto-negotiation. > > link0 not been set before the problem occurred. I reset link0 flag on NAS2 > when I got a problem the first time. > > Now x900 port1.0.12 and bge0 configured automatically. > > >bge1: flags=8843 metric 0 mtu 1500 > > media: Ethernet autoselect (1000baseT ) > > status: active > > >awplus>show int port1.0.12 status > >Port Name Status Vlan Duplex Speed Type > >port1.0.12 connected 55 a-full a-1000 1000BASE-T Would you try attached patch and let me know what you can see on your console? The patch will display error code on console. Note, it may spam your console a lot if you see many RX errors so please don't apply it on your production server. --DBIVS5p969aUjpLe Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="bge.show_err.diff" Index: sys/dev/bge/if_bge.c =================================================================== --- sys/dev/bge/if_bge.c (revision 209211) +++ sys/dev/bge/if_bge.c (working copy) @@ -3382,6 +3382,9 @@ stdcnt++; m = sc->bge_cdata.bge_rx_std_chain[rxidx]; if (cur_rx->bge_flags & BGE_RXBDFLAG_ERROR) { +#if 1 + printf("%04x ", cur_rx->bge_error_flag); +#endif bge_rxreuse_std(sc, rxidx); continue; } --DBIVS5p969aUjpLe--