From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 13:46:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34F2F16A4CE for ; Fri, 11 Mar 2005 13:46:11 +0000 (GMT) Received: from lath.rinet.ru (lath.rinet.ru [195.54.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50C0043D49 for ; Fri, 11 Mar 2005 13:46:10 +0000 (GMT) (envelope-from oleg@rinet.ru) Received: from lath.rinet.ru (localhost [127.0.0.1]) by lath.rinet.ru (8.13.3/8.13.3) with ESMTP id j2BDk9xP086126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 11 Mar 2005 16:46:09 +0300 (MSK) (envelope-from oleg@rinet.ru) Received: from localhost (oleg@localhost) by lath.rinet.ru (8.13.3/8.13.3/Submit) with ESMTP id j2BDk9Yn086123 for ; Fri, 11 Mar 2005 16:46:09 +0300 (MSK) (envelope-from oleg@rinet.ru) Date: Fri, 11 Mar 2005 15:52:29 +0300 (MSK) From: Oleg Bulyzhin To: Dmitry Morozovsky In-Reply-To: <20050310164007.W94235@woozle.rinet.ru> Message-ID: <20050311154312.O83809@lath.rinet.ru> References: <20050310164007.W94235@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed ReSent-Date: Fri, 11 Mar 2005 16:46:02 +0300 (MSK) Resent-From: Oleg Bulyzhin Resent-To: stable@freebsd.org ReSent-Subject: Re: re driver trobles (RELENG_5) ReSent-Message-ID: <20050311164602.R83809@lath.rinet.ru> cc: freebsd-stable@freebsd.org Subject: Re: re driver trobles (RELENG_5) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2005 13:46:11 -0000 On Thu, 10 Mar 2005, Dmitry Morozovsky wrote: > Dear colleagues, > > experimenting with new amd64-based router we found strange re(4) behaviour > when working in autoselect media mode: > > whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 > (depending on STP settings on the switch) network unavailability. > > Moreover, some other re(4) setting changes seem to disturb link state > unneededly (such as ifconfig re0 -vlanhwtag) > > The most annoying fact is that we non-autonegotiating mode with our re and > D-Link gigabit switches: fixing media at 1000BaseTX leads to link down > regardless of master/slave settings on both sides; on re side it is even > undocumented. > > Any clues? > > Thanks in advance. > > Sincerely, > D.Marck [DM5020, MCK-RIPE, DM3-RIPN] > ------------------------------------------------------------------------ > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** > ------------------------------------------------------------------------ Further investigation revealed even more weirdness of re driver: If re card plugged into switch (tested with Catalyst 2948G) with fixed port speed/duplex (100/full) settings, and we trying to reboot - re driver fails to attach: re0: port 0xd000-0xd0ff mem 0xcfffbf00-0xcfffbfff irq 16 at device 11.0 on pci0 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: bpf attached re0: Ethernet address: 00:11:09:cd:15:77 re0: diagnostic failed, failed to receive packet in loopback mode re0: attach aborted due to hardware diag failure rgephy0: detached miibus0: detached device_attach: re0 attach returned 5 If switch port configured for 'auto' mode we can reboot without problems. -- Oleg. ================================================================ === Oleg Bulyzhin -- OBUL-RIPN -- OBUL-RIPE -- oleg@rinet.ru === ================================================================