From owner-freebsd-current@FreeBSD.ORG Wed Dec 26 22:38:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7E6716A4EE for ; Wed, 26 Dec 2007 22:38:17 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: from unixdunk.nesluop.dk (cpe.atm4-0-51450.0x535f05ca.hrnxx12.customer.tele.dk [83.95.5.202]) by mx1.freebsd.org (Postfix) with SMTP id 296F413C4D3 for ; Wed, 26 Dec 2007 22:38:16 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: (qmail 1059 invoked by uid 89); 26 Dec 2007 23:31:14 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by unixdunk.nesluop.dk with SMTP; 26 Dec 2007 23:31:14 -0000 Message-ID: <4772D649.3010001@nesluop.dk> Date: Wed, 26 Dec 2007 23:31:37 +0100 From: Chris Poulsen User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pyunyh@gmail.com References: <476EE604.2070809@nesluop.dk> <20071225234723.GA1018@cdnetworks.co.kr> In-Reply-To: <20071225234723.GA1018@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Problem with nfe stability and throughput 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: Wed, 26 Dec 2007 22:38:17 -0000 Hi, Pyun YongHyeon wrote: > On Sun, Dec 23, 2007 at 11:49:40PM +0100, Chris Poulsen wrote: > > Hi, > > > > I've installed CURRENT on an asus m2n-vm. My network config is giving me > > problems. > > > My dmesg contains: > > > > ata3: [ITHREAD] > > nfe0: port 0xd880-0xd887 mem > > 0xdfffc000-0xdfffcfff,0xdfffe400-0xdfffe4ff,0 > > xdfffe000-0xdfffe00f irq 23 at device 10.0 on pci0 > > miibus0: on nfe0 > > ukphy0: PHY 1 on miibus0 > ^^^^^^ > It seems that ukphy(4) was picked up to serve your PHY hardware. > I guess ukphy(4) is not right phy driver for the hardware as it could > result in non-working driver. Would you show me the ukphy(4) output of > verbosed boot message?(In verbosed boot mode, ukphy(4) may have printed > OUI/model number of the PHY hardware.) > > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto > > nfe0: Ethernet address: 00:1d:60:6d:73:ec > > A verbose boot log contains the following: ... ata3: [ITHREAD] nfe0: port 0xd880-0xd887 mem 0xdfffc000-0xdfffcfff,0xdfffe400-0xdfffe4ff,0xdfffe000-0xdfffe00f irq 23 at device 10.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfffc000 nfe0: attempting to allocate 8 MSI vectors (8 supported) msi: routing MSI IRQ 256 to vector 56 msi: routing MSI IRQ 257 to vector 57 msi: routing MSI IRQ 258 to vector 58 msi: routing MSI IRQ 259 to vector 59 msi: routing MSI IRQ 260 to vector 60 msi: routing MSI IRQ 261 to vector 61 msi: routing MSI IRQ 262 to vector 62 msi: routing MSI IRQ 263 to vector 63 nfe0: using IRQs 256-263 for MSI nfe0: Using 8 MSI messages miibus0: on nfe0 ukphy0: PHY 1 on miibus0 ukphy0: OUI 0x001374, model 0x0001, rev. 6 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto nfe0: bpf attached nfe0: Ethernet address: 00:1d:60:6d:73:ec nfe0: [MPSAFE] nfe0: [FILTER] ... Also I noticed that both nfe0 and ohci1 both lists irq 23, but I don't know if that is a problem :) ... ohci1: mem 0xdfffd000-0xdfffdfff irq 23 at device 4.0 on pci0 ... What would be the next step for me to try in order to resolve this? Thanks. -- Regards Chris