From owner-freebsd-current@FreeBSD.ORG Sun Mar 11 08:09:54 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 8B48716A4C0 for ; Sun, 11 Mar 2007 08:09:54 +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 20A1813C461 for ; Sun, 11 Mar 2007 08:09:54 +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.63) (envelope-from ) id 1HQJ7n-00014n-0w; Sun, 11 Mar 2007 09:09:51 +0100 Message-ID: <45F3B94B.3030104@gwdg.de> Date: Sun, 11 Mar 2007 09:09:47 +0100 From: Rainer Hurling User-Agent: Thunderbird 1.5.0.10 (X11/20070306) 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> In-Reply-To: <20070311050627.GC79728@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: Sun, 11 Mar 2007 08:09:54 -0000 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? 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? Rainer Hurling