tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: gigE negotiation failure with wm0
On Tue, 9 Sep 2008 17:41:57 -0400
Brad <brad%comstyle.com@localhost> wrote:
> On Tue, 9 Sep 2008 11:07:51 -0500
> David Young <dyoung%pobox.com@localhost> wrote:
>
> > On Tue, Sep 09, 2008 at 11:44:31AM -0400, Steven M. Bellovin wrote:
> > > Here are the wm0 and phy lines from dmesg:
> > >
> > > wm0 at pci0 dev 25 function 0: Intel i82801H (M_AMT) LAN
> > > Controller, rev. 3 wm0: interrupting at ioapic0 pin 20 (irq 11)
> > > wm0: PCI-Express bus
> > > wm0: FLASH
> > > wm0: Ethernet address 00:1e:37:18:93:c5
> > > igphy0 at wm0 phy 1: i82566 10/100/1000 media interface, rev. 0
> > > igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> > > 1000baseT-FDX, auto
> >
> > Steven,
> >
> > Christoph Egger mentioned this patch to me, yesterday,
> >
> > http://article.gmane.org/gmane.os.openbsd.cvs/79169
> >
> > I have not looked into it, so I don't know if it may help your
> > problem or not.
> >
> > Dave
>
> This will not help with the problem. Looking at igphy(4) I can see it
> is programming DSP override values into the third generation IGP PHY
> which it should not. First I would make the code only call the DSP
> load function for the first two generations of PHY (represented by a
> single PHY id). Then I would also take a look at...
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/e1000/e1000_phy.c
>
> e1000_phy_init_script_igp3() and create another DSP load function for
> the third generation PHY and plug in those DSP values.
>
Interesting. Running with ukphy at home, I'm happily speaking GigE,
and getting ttcp throughput of >750M bps in one direction (the other
end is i386-current with bge0) and 600M bps in the other. I'll see
what happens tomorrow with the problematic switch. But -- do I lose
anything by using ukphy instead of igphy?
--Steve Bellovin, http://www.cs.columbia.edu/~smb
Home |
Main Index |
Thread Index |
Old Index