From owner-freebsd-current@FreeBSD.ORG Thu Jan 17 18:05:21 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 9F6F616A419 for ; Thu, 17 Jan 2008 18:05:21 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: from unixdunk.nesluop.dk (cpe.atm4-0-51450.0x535f05ca.hrnxx12.customer.tele.dk [83.95.5.202]) by mx1.freebsd.org (Postfix) with SMTP id 000F213C4D3 for ; Thu, 17 Jan 2008 18:05:19 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: (qmail 2545 invoked by uid 89); 17 Jan 2008 18:05:14 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by unixdunk.nesluop.dk with SMTP; 17 Jan 2008 18:05:14 -0000 Message-ID: <478F98D7.5040007@nesluop.dk> Date: Thu, 17 Jan 2008 19:05:11 +0100 From: Chris Poulsen User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pyunyh@gmail.com 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> In-Reply-To: <20080117014013.GA89210@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2008 18:05:21 -0000 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 > > 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) ... Things seemed to still be running, but ping to another local machine was sloooow. HTH. -- Regards Chris