From owner-freebsd-current@FreeBSD.ORG Fri Jan 18 01:01:08 2008 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 6E5B216A41A for ; Fri, 18 Jan 2008 01:01:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 2840313C448 for ; Fri, 18 Jan 2008 01:01:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1399511waf.3 for ; Thu, 17 Jan 2008 17:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=wE4Z5vQg+DZNIdwV+Jpul7xLSsR23GFt26H31R5fNQM=; b=A3p4LZDoAZyFbTuayMZpR4nkog04x6aKjBDbUFBsQVdD85/5Wpd5m6wJbOUAVRunCx/eiUNCc3aOvZx/X3WKZPxTX4MvgOESt0kMB84SKTV2+ODX9D2Gu7itn3b9cDWUY3ZHcpuoYvHyLuRj4W5rNMWshTcuvnNSJj6uWO7Mcc4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=Sqkmy5hAIrJ0RP+yoDdPKt9SZO4L4ZnZa0E8yDoOpS8kCAeb1Rz6u/RqOx1R1WI58z4NiMSZ5lrcbBXXDpOef+i2l3nWpLEhoktXOYMQZV1vkQCnFMEI0+fm0L/Im0mJHE5NhasY1IXU81jMXMhCk7bZBBreErkdp7Zqfid67hk= Received: by 10.114.144.1 with SMTP id r1mr3174213wad.53.1200618067900; Thu, 17 Jan 2008 17:01:07 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k26sm5955782waf.58.2008.01.17.17.01.05 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Jan 2008 17:01:06 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0I11127093009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Jan 2008 10:01:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0I110LC093008; Fri, 18 Jan 2008 10:01:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 18 Jan 2008 10:01:00 +0900 From: Pyun YongHyeon To: Chris Poulsen Message-ID: <20080118010100.GC92718@cdnetworks.co.kr> References: <476EE604.2070809@nesluop.dk> <20071225234723.GA1018@cdnetworks.co.kr> <4772D649.3010001@nesluop.dk> <20071227002252.GE1018@cdnetworks.co.kr> <20080116012154.GB84758@cdnetworks.co.kr> <478E7DF3.4080908@nesluop.dk> <20080117014013.GA89210@cdnetworks.co.kr> <478F98D7.5040007@nesluop.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <478F98D7.5040007@nesluop.dk> User-Agent: Mutt/1.4.2.1i Cc: kevlo@freebsd.org, FreeBSD Current Subject: Re: Problem with nfe stability and throughput 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: Fri, 18 Jan 2008 01:01:08 -0000 On Thu, Jan 17, 2008 at 07:05:11PM +0100, Chris Poulsen wrote: > Hi, > > Pyun YongHyeon wrote: > >Would you show me the output of "ifconfig nfe0"? > > > nfe0: flags=8843 metric 0 mtu 1500 > options=48 > ether 00:1d:60:6d:73:ec > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet 100baseTX > status: active Hmmm, it seems that you've set media type manually without relying on automatic media detection. Is there any reason not using auto media type? How about using media type 'auto'? #ifconfig nfe0 media auto > > > > What do you need me to do, in order to get some usable info about what > > > is going on? > > > > > > >What about changing /usr/src/sys/dev/mii/atphy.c as the following? > >From atphy.c, line number 174: > >171 /* > >172 * Reset the PHY so all changes take effect. > >173 */ > >174 if (IFM_SUBTYPE(ife->ifm_media) != IFM_AUTO) { > >175 bmcr = PHY_READ(sc, MII_BMCR); > >176 PHY_WRITE(sc, MII_BMCR, bmcr | BMCR_RESET); > >177 } > >178 break; > > > >To: > >171 /* > >172 * Reset the PHY so all changes take effect. > >173 */ > >174 bmcr = PHY_READ(sc, MII_BMCR); > >175 PHY_WRITE(sc, MII_BMCR, bmcr | BMCR_RESET); > >176 break; > > > >As you know, no public documentation for the phy is available so > >it would take long time to find a clue to support the hardware. > >Please don't give up and lets try possible (still guessing) > >combinations. > > > > > Tried the changes. Things came up just fine. Ftp transfer worked, well > my machine had a panic after 3 big files, but as far as i could tell it > was zfs related (I was dropping the files on my zfs test partition ;)) > > Ftp client reported transfer speeds around 8,7 megabyte/sec until the > panic. After a reboot I tried ssh/sftp and things ran seemingly stable. > So I decided to beat it up with a torrent download :) > Finally I managed to get some text in my logs ;) : > .... > kernel: nfe0: discard frame w/o leading ethernet header (len 4294967295 > pkt len 4294967295) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > last message repeated 9 times > kernel: nfe0: discard frame w/o leading ethernet header (len 4294967295 > pkt len 4294967295) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > last message repeated 10 times > kernel: nfe0: discard frame w/o leading ethernet header (len 7 pkt len 7) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > last message repeated 7 times > kernel: nfe0: discard frame w/o leading ethernet header (len 6 pkt len 6) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > kernel: nfe0: discard frame w/o leading ethernet header (len 4 pkt len 4) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > last message repeated 7 times > kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > last message repeated 4 times > kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > ... > nfe(4) has a long standing issue not correctly handling half-duplex media in manual media configuration. I guess the above issue is related with your manual media configuration such that nfe(4) thinks it established a full-duplex link with link partner but the resolved link is still half-duplex one. > Things seemed to still be running, but ping to another local machine was > sloooow. > Yep, it's getting closer to working state. :) -- Regards, Pyun YongHyeon