From owner-freebsd-current@FreeBSD.ORG Fri Jan 18 18:17:38 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 55BCA16A41A for ; Fri, 18 Jan 2008 18:17:38 +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 8719D13C447 for ; Fri, 18 Jan 2008 18:17:37 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: (qmail 1496 invoked by uid 89); 18 Jan 2008 18:10:48 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by unixdunk.nesluop.dk with SMTP; 18 Jan 2008 18:10:48 -0000 Message-ID: <4790EBA8.9090500@nesluop.dk> Date: Fri, 18 Jan 2008 19:10:48 +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> <478F98D7.5040007@nesluop.dk> <20080118010100.GC92718@cdnetworks.co.kr> <20080118082609.GA93423@cdnetworks.co.kr> In-Reply-To: <20080118082609.GA93423@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: Fri, 18 Jan 2008 18:17:38 -0000 Hi, Pyun YongHyeon wrote: > On Fri, Jan 18, 2008 at 10:01:00AM +0900, To Chris Poulsen wrote: > > 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 > > > > I've updated the experimental driver. Please revert previous patch and > apply the following one. > > http://people.freebsd.org/~yongari/atphy.diff2 > > And show me the 'ifconfig nfe0' output again. > I tried specifying the media type manually, when I was trying to get nfe up and running earlier, I've reverted to auto now. The box in question is currently running with your latest patch, I did manage to stress it (with a couple of concurrent ftp uploads+some web browing) into a state where it once again gave me a bunch of the following: 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 12 times kernel: nfe0: discard frame w/o leading ethernet header (len 3 pkt len 3) kernel: nfe0: discard frame w/o leading ethernet header (len 11 pkt len 11) kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) kernel: nfe0: link state changed to DOWN kernel: nfe0: link state changed to UP However bringing the interface down and up seemed to put it back into a normal state. (I just noticed that nfe0 went down/up again, without my interaction, if that matters). ifconfig nfe0 yields: 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 autoselect (100baseTX ) status: active -- Regards Chris