Problem with nfe stability and throughput

Pyun YongHyeon pyunyh at gmail.com
Tue Jan 15 17:27:38 PST 2008


On Thu, Dec 27, 2007 at 09:22:52AM +0900, To Chris Poulsen wrote:
 > 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).
 > 

Based on hardware information from Linux l1 driver I wrote a simple
PHY driver. You can get the diff at the following URL.
Would you give it spin?

http://people.freebsd.org/~yongari/atphy.diff

Note, I don't have the hardware so don't know whether it works or
not. Just compile tested. I also have no PHY hardware information
so the model name in the driver may not reflect real name.

-- 
Regards,
Pyun YongHyeon


More information about the freebsd-current mailing list