From owner-freebsd-current@FreeBSD.ORG Mon Mar 12 04:49:15 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 763B316A406 for ; Mon, 12 Mar 2007 04:49:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 2D4FE13C45A for ; Mon, 12 Mar 2007 04:49:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1183699ana for ; Sun, 11 Mar 2007 21:49:14 -0700 (PDT) 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=m3cBCXnJu24eAD1G1ARSWd12cEhR/vhZhbpLbniQn+/h7FHv6Fg3J09A0o/mC0vq3I/RKW80kAP/I+Jrlags/tIwi4YOW/vhPR0tmzLo3PojVnapH1/igzyyYohpy+CXAyLBqUzriQ1KOFbRZwG7mWdOB82OecZ/pq7onFTiQt8= 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=OgTs7/AbXA+s/4UnLT2/K7OuPpuNKNprEpOhy6EX9rXiuYnUSAPzK0E10QiyBbsFs2ow2+naZlFrcrmWOTBGTN+CdzXjRzGbvlVu/Mv2wZhPaXsFul3QjWdJB018VxdkB5tXshkkGe8v+hvxVfJVT8nGl0UMIPqK+nLlQUswW14= Received: by 10.35.38.17 with SMTP id q17mr2576645pyj.1173674954324; Sun, 11 Mar 2007 21:49:14 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 5sm27501172nzk.2007.03.11.21.49.11; Sun, 11 Mar 2007 21:49:13 -0700 (PDT) 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 l2C4pJFI084477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Mar 2007 13:51:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l2C4pGDR084476; Mon, 12 Mar 2007 13:51:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 12 Mar 2007 13:51:16 +0900 From: Pyun YongHyeon To: Rainer Hurling Message-ID: <20070312045116.GA83433@cdnetworks.co.kr> References: <20070310074734.GC70613@cdnetworks.co.kr> <917080.87242.qm@web34701.mail.mud.yahoo.com> <20070311050627.GC79728@cdnetworks.co.kr> <45F3B94B.3030104@gwdg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45F3B94B.3030104@gwdg.de> User-Agent: Mutt/1.4.2.1i 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 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: Mon, 12 Mar 2007 04:49:15 -0000 On Sun, Mar 11, 2007 at 09:09:47AM +0100, Rainer Hurling wrote: > Pyun YongHyeon schrieb: > >[... SNIP ...] > > > >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. > > > Yes, nfe(4) works on MCP55, but with some strange behaviour, see below. > > I am working with FreeBSD 7.0-CURRENT from 03/07/2007 on MSI K9N Neo. > 'dmesg | grep nfe' gives me: > > nfe0: port 0xb000-0xb007 mem > 0xfbef7000-0xfbef7fff,0xfbefa800-0xfbefa8ff,0xfbefa400-0xfbefa40f irq 21 > at device 8.0 on pci0 > miibus0: on nfe0 > ukphy0: PHY 1 on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > nfe0: using obsoleted if_watchdog interface > nfe0: Ethernet address: xx:xx:xx:xx:xx:xx > nfe0: [ITHREAD] > > It seems that there is a problem with watchdog. Perhaps the choosen > media interface ukphy0 is not correct? > Normally nVidia GigEs use Marvell PHY which is served by e1000phy(4) so I guess power saving mode had ukphy attach the PHY. Booting/loading module with bootverbose mode will show up OUI/model/rev of the PHY. Please let me know the OUI/model/rev output of ukphy(4). > In the context with watchdog I observe an interesting behaviour of nfe0: > After running WindowsXP on my board, I am not able to use the interface > any more. Booting FreeBSD always gives me messages like this: > > ----- > nfe0: link state changed to DOWN > /etc/rc.d/dhclient: WARNING: $background_dhclient_nfe0 is not set > properly - > see > rc.conf(5). > nfe0: no link ....nfe0: link state changed to UP > got link > DHCPREQUEST on nfe0 to 255.255.255.255 port 67 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPREQUEST on nfe0 to 255.255.255.255 port 67 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 5 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 > nfe0: link state changed to UP > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 14 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 18 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 9 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > nfe0: link state changed to UP > DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 6 > nfe0: watchdog timeout > nfe0: link state changed to DOWN > No DHCPOFFERS received. > Trying recorded lease xxx.xxx.xxx.xxx > nfe0: link state changed to UP > bound: renewal in 429590 seconds. > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > nfe0: flags=8843 metric 0 mtu 1500 > options=2b > ether xx:xx:xx:xx:xx:xx > media: Ethernet autoselect (100baseTX ) > status: active > ----- > > When booting 'cold' (means full power down) FreeBSD is able to use > nfe(4) in the correct way. Also booting FreeBSD again after running > FreeBSD gives me no errors. Obviously WindowsXP does not clear up all > registers in MCP55 after leaving? > I think Windows put the NIC/PHY in sleep/power saving mode and nfe(4) will need a way to take PHY/NIC out of power down mode. Try a WIP version at the following URL. http://people.freebsd.org/~yongari/nfe/WIP/if_nfe.c http://people.freebsd.org/~yongari/nfe/WIP/if_nfereg.h http://people.freebsd.org/~yongari/nfe/WIP/if_nfevar.h Note, it's just guess work from the Linux driver and I just tested compilation. Due to lack of time/MCP55 hardware it's not easy for me to fix. > Rainer Hurling -- Regards, Pyun YongHyeon