From owner-freebsd-current@FreeBSD.ORG Sat Mar 31 15:06:26 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3E5F16A404 for ; Sat, 31 Mar 2007 15:06:25 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from tmailer.gwdg.de (tmailer.gwdg.de [134.76.10.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8ACDB13C45A for ; Sat, 31 Mar 2007 15:06:25 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [87.139.104.184] (helo=[192.168.2.20]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1HXf50-0000WX-7c; Sat, 31 Mar 2007 17:01:22 +0200 Message-ID: <460E77BE.9090503@gwdg.de> Date: Sat, 31 Mar 2007 17:01:18 +0200 From: Rainer Hurling User-Agent: Thunderbird 1.5.0.10 (X11/20070318) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20070310074734.GC70613@cdnetworks.co.kr> <917080.87242.qm@web34701.mail.mud.yahoo.com> <20070311050627.GC79728@cdnetworks.co.kr> <45F3B94B.3030104@gwdg.de> <20070312045116.GA83433@cdnetworks.co.kr> <45F5C914.3000805@gwdg.de> <20070313004601.GA87608@cdnetworks.co.kr> <20070313005845.GB87608@cdnetworks.co.kr> <45F636B5.9060608@gwdg.de> <20070313070153.GD87608@cdnetworks.co.kr> <20070331003031.GB68853@cdnetworks.co.kr> In-Reply-To: <20070331003031.GB68853@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: darren780@yahoo.com, freebsd-current@freebsd.org Subject: Re: yongari nfe problems 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: Sat, 31 Mar 2007 15:06:26 -0000 Thank you Pyun YongHyeon for the newest patch. I am running it with if_nfe.c and if_nfereg.h from 03/21/2007 and if_nfevar.h from 03/19/2007 on FreeBSD 7.0-CURRENT (i386) from today. boot -v gives me: nfe0: port 0xb000-0xb007 mem xfbef3000-0xfbef3fff,0xfbefa800-0xfbefa8ff,0 xfbefa400-0xfbefa40f irq 22 at device 8.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfbef3000 miibus0: on nfe0 ciphy0: PHY 1 on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: bpf attached nfe0: Ethernet address: 00:16:17:95:d9:7c nfe0: [MPSAFE] nfe0: [FILTER] Now there are no more warning from miibus0 :-) Unfortunately at bigger network transfers I still observe the previously described watchdog timeouts: nfe0: watchdog timeout (missed Tx interrupts) -- recovering nfe0: watchdog timeout (missed Tx interrupts) -- recovering nfe0: watchdog timeout (missed Tx interrupts) -- recovering nfe0: watchdog timeout (missed Tx interrupts) -- recovering nfe0: watchdog timeout (missed Tx interrupts) -- recovering nfe0: watchdog timeout (missed Tx interrupts) -- recovering ... During these timeouts I am not able to use my network ;-( I would be happy if I could help solving this problem. Let me know if I can test anything. Thank you so long, Rainer Pyun YongHyeon schrieb: > On Tue, Mar 13, 2007 at 04:01:53PM +0900, To Rainer Hurling wrote: > > On Tue, Mar 13, 2007 at 06:29:25AM +0100, Rainer Hurling wrote: > > > Over night my systems works well, only one message from network came up: > > > > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > > > > > I'm not sure this watchdog is related with VSC8601 PHY. > > However Mr. Darren also reported watchdog errors on MCP55 so I have > > to think again what makes MCP55 different. > > > > > In the morning I tried your patch for mii and PHY. Bootingverbose again > > > gives me: > > > > > > nfe0: port 0xb000-0xb007 mem > > > 0xfbef3000-0xfbef3fff,0xfbefa800-0xfbefa8ff,0 > > > xfbefa400-0xfbefa40f irq 22 at device 8.0 on pci0 > > > nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfbef3000 > > > nfe0: bpf attached > > > nfe0: Ethernet address: 00:16:17:95:d9:7c > > > miibus0: on nfe0 > > > ciphy0: PHY 1 on miibus0 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > 1000baseT-FDX, auto > > > nfe0: [MPSAFE] > > > nfe0: [FILTER] > > > > > > > > > First, all seems to be ok. Network was up and connected. After a minute > > > I lost connection and the following messages appeared: > > > > > > miibus0: unknown CICADA PHY model 2 > > > miibus0: unknown CICADA PHY model 2 > > > miibus0: unknown CICADA PHY model 2 > > > > Sorry, you can ignore this. I've ommitted a code needed in fixup code > > for VSC8601. > > > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > nfe0: watchdog timeout (missed Tx interrupts) -- recovering > > > ... > > > > > > > This is real problem. I guess ciphy(4) failed to report correct link > > state so watchdog handler was activated. Apparently we **NEED** a copy > > of the documentation for the PHY. :-( > > You can revert the PHY changes and use ukphy(4) until the issue is > > resolved. > > > > Would you try updated ciphy(4) patch? > I've got a successful report from nfe(4)/CS8201 user. > > > > > > > Probably a little more work on the patches is needed? > > > > > > > Yes, ciphy(4) should be educated to access magic registers. > > > > > I am offline for the next ten hours. After that I could test any new > > > version ;-) > > > > > > > I'll let you know if I have a patch for the watchdog errors. In these > > days I have little time to focus on FreeBSD stuff so don't expect > > quick reply. > > Thank you very much for testing and your time. > > > > > Thank you very much, > > > Rainer > > > > > -- > > Regards, > > Pyun YongHyeon >