Re: ale(4) cannot negotiate as GigE

On Wed, Feb 20, 2013 at 01:37:39PM +0900, YongHyeon PYUN wrote:
> On Tue, Feb 19, 2013 at 08:23:02AM +0000, Alexey Dokuchaev wrote:
> > ale0_at_pci0:2:0:0:        class=0x020000 card=0x82261043 chip=0x10261969
> > rev=0xb0 hdr=0x00
> >     vendor     = 'Atheros Communications Inc.'
> >     device     = 'AR8121/AR8113/AR8114 Gigabit or Fast Ethernet'
> >     class      = network
> >     subclass   = ethernet
> > 
> > According the the specs, it should be GigE. [...]
> 
> There is a fast etherenet version(L2E) so I'm not sure what you
> have. Could you show me dmesg output(ale(4) & atphy(4) only) and
> "devinfo -rv | grep atphy"?

$ dmesg | egrep ale\|atphy
ale0: <Atheros AR8121/AR8113/AR8114 PCIe Ethernet> port 0xcc00-0xcc7f mem 0xfe9c0000-0xfe9fffff irq 17 at device 0.0 on pci2
ale0: 960 Tx FIFO, 1024 Rx FIFO
ale0: Using 1 MSI messages.
ale0: 4GB boundary crossed, switching to 32bit DMA addressing mode.
miibus0: <MII bus> on ale0
atphy0: <Atheros F1 10/100/1000 PHY> PHY 0 on miibus0
atphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow

$ devinfo -rv | grep atphy
                atphy0 pnpinfo oui=0xc82e model=0x1 rev=0x9 at phyno=0

> > I'm not sure why it happens; maybe it's somehow related to a handful of
> > those "ale0: link state changed to DOWN/UP" flip-flops I see in dmesg(8),
> > before it can finally obtain DHCP lease?
> 
> That's normal when you initiate auto-negotiation with dhclient.

Yes, I've already seen your lengthy explanation [1], thanks!

> > I remember these adapters had problems in the past, like infamous
> > "Corrupted MAC on input" disconnect messages, but I don't recall that I
> > could not use it in GigE mode. [...]
> 
> If you still see the "Corrupted MAC on input" message, let me know.

No, those are long gone now (hopefully; at least I haven't seen them for a
while).

./danfe

[1] http://lists.freebsd.org/pipermail/freebsd-net/2009-January/020662.html