Date: Thu, 27 Dec 2007 09:22:52 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Chris Poulsen <mailinglist@nesluop.dk> Cc: kevlo@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Problem with nfe stability and throughput Message-ID: <20071227002252.GE1018@cdnetworks.co.kr> In-Reply-To: <4772D649.3010001@nesluop.dk> References: <476EE604.2070809@nesluop.dk> <20071225234723.GA1018@cdnetworks.co.kr> <4772D649.3010001@nesluop.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 26, 2007 at 11:31:37PM +0100, Chris Poulsen wrote:
> 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.
> > <snip>
> > > My dmesg contains:
> > >
> > > ata3: [ITHREAD]
> > > nfe0: <NVIDIA nForce MCP67 Networking Adapter> port 0xd880-0xd887 mem
> > > 0xdfffc000-0xdfffcfff,0xdfffe400-0xdfffe4ff,0
> > > xdfffe000-0xdfffe00f irq 23 at device 10.0 on pci0
> > > miibus0: <MII bus> on nfe0
> > > ukphy0: <Generic IEEE 802.3u media interface> 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
> ><snip>
> >
> A verbose boot log contains the following:
> ...
> ata3: [ITHREAD]
> nfe0: <NVIDIA nForce MCP67 Networking Adapter> 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: <MII bus> on nfe0
> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
> ukphy0: OUI 0x001374, model 0x0001, rev. 6
^^^^^^^^^^^^^^^^^^^^^^^^^^
According to IEEE stanards OUI database the manufacturer is Atheros
Communications. Since Atheros acquired Attansic Technology I guess
the phy originated from Attansic Technology. ATM there is no phy
driver for FreeBSD and the vendor didn't release publicly available
datasheets to developers. AFAIK kevlo is working on Attansic driver
so I guess he may have more information for this phy hardware(CCed).
> 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 :)
Don't worry about that. Your nfe(4) takes advantage of MSI so there
is no IRQ sharing.
> ...
> ohci1: <OHCI (generic) USB controller> 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
--
Regards,
Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071227002252.GE1018>