From owner-freebsd-current@FreeBSD.ORG Sun Mar 11 05:04:36 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 AB8A516A400 for ; Sun, 11 Mar 2007 05:04:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 3921513C441 for ; Sun, 11 Mar 2007 05:04:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1470685nfc for ; Sat, 10 Mar 2007 21:04:35 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=Ai9Q0dQDWI/KQyXEKNXy/KDu9R6dWTmfY7fUEnukJ7liJ9Q+K14cgcNEWT30yopApewLmFRFLKU5LfJTnQF+N0x8w+UVeZOSoXHns/Fq0XQKg+ZCBdNw75N6K7N4+U/P8qfw5FM9uBdWMQ2+mI+r5FMqhYKl0cGek4Jda0qXOoQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=lt3JV0QFgwfQnp8nP/oIdQjhUm9W4HWJo5bim2Muofb/qf6YvY7g8TVPK4ecdb1NA2uNkcycvkvZamLX3Kt7Irt6kkcPbtaLVWkfw/JpnALX02qYa8HZSxA+y+z6xUZSMQiqMtWfqwL9mcCUOOr58FCWjC1ko7upNeAPx82yPOI= Received: by 10.114.201.1 with SMTP id y1mr700431waf.1173589474319; Sat, 10 Mar 2007 21:04:34 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id n22sm13096966pof.2007.03.10.21.04.32; Sat, 10 Mar 2007 21:04:33 -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 l2B56R3w080224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Mar 2007 14:06:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l2B56RNe080223; Sun, 11 Mar 2007 14:06:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sun, 11 Mar 2007 14:06:27 +0900 From: Pyun YongHyeon To: "Mr. Darren" Message-ID: <20070311050627.GC79728@cdnetworks.co.kr> References: <20070310074734.GC70613@cdnetworks.co.kr> <917080.87242.qm@web34701.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <917080.87242.qm@web34701.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: yongari nfe problems 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: Sun, 11 Mar 2007 05:04:36 -0000 On Sat, Mar 10, 2007 at 07:13:12AM -0800, Mr. Darren wrote: > > --- Pyun YongHyeon wrote: > > > On Fri, Mar 09, 2007 at 10:21:45PM -0800, Mr. Darren > > wrote: > > > > > > --- Pyun YongHyeon wrote: > > > > > > > On Fri, Mar 09, 2007 at 08:08:56PM +0900, To > > Mr. > > > > Darren wrote: > > > > > On Thu, Mar 08, 2007 at 04:33:36PM -0800, > > Mr. > > > > Darren wrote: > > > > > > I tried the following overhauled nfe > > drivers > > > > after no > > > > > > success in getting nfe to work with my > > > > hardware. > > > > > > > > > > > http://people.freebsd.org/~yongari/nfe/if_nfe.c > > > > > > > > > > > > > > > > > > > > > > > > > http://people.freebsd.org/~yongari/nfe/if_nfereg.h > > > > > > > > > > > > > > > > > > > > > > > > > http://people.freebsd.org/~yongari/nfe/if_nfevar.h > > > > > > > > > > > > It still doesn't work, but I have a new > > set of > > > > errors. > > > > > > > > > > > > nfe0: > Adapter> > > > > port > > > > > > 0xb000-0xb007 mem > > > > > > > > > > > > > > > > 0xfe02a000-0xfe02afff,0xfe029000-0xfe0290ff,0xfe028000-0xfe02800f > > > > > > irq 10 at device 16.0 on pci0 > > > > > > nfe0: Ethernet address: 00:15:f2:f4:af:5e > > > > > > miibus1: on nfe0 > > > > > > nfe0: [ITHREAD] > > > > > > nfe1: > Adapter> > > > > port > > > > > > 0xac00-0xac07 mem > > > > > > > > > > > > > > > > 0xfe027000-0xfe027fff,0xfe026000-0xfe0260ff,0xfe025000-0xfe02500f > > > > > > irq 11 at device 17.0 on pci0 > > > > > > nfe1: Ethernet address: 00:15:f2:f4:af:5f > > > > > > miibus2: on nfe1 > > > > > > nfe1: [ITHREAD] > > > > > > nfe0: link state changed to DOWN > > > > > > nfe0: link state changed to UP > > > > > > nfe0: watchdog timeout (missed Tx > > interrupts) > > > > -- > > > > > > recovering > > > > > > nfe0: watchdog timeout (missed Tx > > interrupts) > > > > -- > > > > > > recovering > > > > > > > > > > > > > > > > According to Shigeaki Tagashira'page nForce > > 590 > > > > is supported by > > > > > nfe(4). ATM I have no idea why it shows > > watchdog > > > > timeout errors. > > > > > Btw, I don't see what PHY driver was > > attached in > > > > your message. > > > > > (You can check it with dmesg(8) and normally > > it > > > > would pick up > > > > > e1000phy(4).) > > > > > > > > > > > > > Oops, I think I've posted wrong version. > > > > Please re-fetch and try again. > > > > > > > > > > > > > > > > the missing tx interrupts were made while > > > > trying > > > > > > /sbin/dhclient nfe0 > > > > > > > > > > > > My motherboard is the ASUS crosshair > > NVIDIA > > > > nForce 590 > > > > > > FreeBSD DARREN 7.0-CURRENT FreeBSD > > 7.0-CURRENT > > > > #12: > > > > > > Thu Mar 8 16:57:38 UTC 2007 > > > > > > root@DARREN:/usr/obj/usr/src/sys/DARREN > > amd64 > > > > > > the cvsup this kernel was compiled with > > is > > > > less than 1 > > > > > > week old. > > > > > > > > > > > > -Darren > > > > > -- > > > > > Regards, > > > > > Pyun YongHyeon > > > > > > > > -- > > > > Regards, > > > > Pyun YongHyeon > > > > > > > > > > > > > e1000phy0: PHY 1 on > > > miibus1 > > > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, > > > 100baseTX-FDX, 1000baseTX-FDX, auto > > > e1000phy1: PHY 1 on > > > miibus2 > > > e1000phy1: 10baseT, 10baseT-FDX, 100baseTX, > > > 100baseTX-FDX, 1000baseTX-FDX, auto > > > > > > same problem with the new driver downloaded from > > > http://people.freebsd.org/~yongari/nfe/ . again, > > > while /sbin/dhclient nfe0 while in communication > > to my > > > router. > > > > > > nfe0: link state changed to DOWN > > > nfe0: link state changed to UP > > > 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 > > > > > > > Before starting dhclient(8) would you run 'ifconfig > > up nfe0' and > > check media status? Does it reports correct media > > speed/duplex > > settings? > > > > -- > > Regards, > > Pyun YongHyeon > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > > > ran ifconfig nfe0 up, the media is correct. > media: Ethernet autoselect (100baseTX > ) > attempted /sbin/dhclient nfe0 with the same results as > before. > Did stock nfe(4) work on MCP55? (I'm not interested in how nve(4) works on MCP55.) I'm afraid MCP55 requires different programming. Searching archives for Linux forcedeth driver also reveals issues on MCP55 which is exactly the same issue I think. I'll let you know if I find a clue but it's hard to fix due to lack of MCP55 hardware and documentation. -- Regards, Pyun YongHyeon