From owner-freebsd-current@FreeBSD.ORG Sat Mar 10 07:45:56 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 BBCF316A400 for ; Sat, 10 Mar 2007 07:45:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 4BBBC13C471 for ; Sat, 10 Mar 2007 07:45:56 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so1519317ugh for ; Fri, 09 Mar 2007 23:45:55 -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=TEfiYaV7yiE0N7tcc656R7wx3nkZjVBuWJiYTuDEuGcqvjuHPkKPhh/Rrbz5oZWbewRt1VYouHy2QwvqOi+dAjQp8ah4UraEQjarg8E1CorvUOLMyraPYJXgDCmwcpK1fdR0xffwe8ciT39YecDcmRjYLNneRnsvKDT1V6OEsYM= 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=JrGGAr6lm2TBrMjFAsJUQyQLyT5Jt7vm8xZuj1Erg1odKjhjV4wtKoYzirEfdt0V27UDNsAssfMghQZDAGCMAaiRzinyuY0Xr6SNam75lj9NrFuOPq2wk/TZ7WqWIWqoP9hL8CUKEHf03HPytvU4BO8tek+SZ8LuJdB5bbBPImQ= Received: by 10.114.181.1 with SMTP id d1mr107918waf.1173512753987; Fri, 09 Mar 2007 23:45:53 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id a8sm10523889poa.2007.03.09.23.45.51; Fri, 09 Mar 2007 23:45:52 -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 l2A7lZ0e076853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Mar 2007 16:47:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l2A7lZFD076852; Sat, 10 Mar 2007 16:47:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 10 Mar 2007 16:47:35 +0900 From: Pyun YongHyeon To: "Mr. Darren" Message-ID: <20070310074734.GC70613@cdnetworks.co.kr> References: <20070310022914.GB70613@cdnetworks.co.kr> <133119.17197.qm@web34705.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <133119.17197.qm@web34705.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: Sat, 10 Mar 2007 07:45:56 -0000 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: > > 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: > > 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