Re: Call for testers : age(4), Attansic/Atheros L1 gigabit ethernet controller

On Thu, 13 Mar 2008, Pyun YongHyeon wrote:

> On Mon, Mar 10, 2008 at 04:31:50PM +0900, To freebsd-current_at_FreeBSD.org wrote:
>  > On Mon, Mar 10, 2008 at 01:34:12PM +0900, To freebsd-current_at_FreeBSD.org wrote:
>  >  > Hi,
>  >  >
>  >  > Due to high pressure from FreeBSD user community to get a working
>  >  > driver for Attansic/Atheros L1 giagabit ethernet I had changed
>  >  > priorities in my TODO list. I had spent several weeks to write
>  >  > this driver and I managed to get a working driver. From my very
>  >  > limited testing the driver seems to work as expected.
>  >  >
>  >  > ATM the performance is horrible so there must be mis-programmed
>  >  > registers or incorrectly configured parameters. Due to the
>  >  > existence several variants of L1 hardware and lack of publicly
>  >  > available documentation I'd like to know how many variants are
>  >  > supported by this driver. L1 gigabit ethernet controller is
>  >  > frequently found in ASUS motherboard. Note, it seems that there are
>  >  > other variants of hardware as known as L2(Fast ethernet) and newer
>  >  > gigabit ethernet(AR81xx) from Atheros. These are not supported by
>  >  > this driver and they require a seperate driver. The following
>  >  > hardware features are supported by age(4).
>  >  >
>  >  >   - TCP Segmentation Offload.
>  >  >   - Hardware VLAN tag insertion/stripping.
>  >  >   - TCP/UDP checksum offload.
>  >  >   - Interrupt moderation.
>  >  >   - Hardware statistics counter support.
>  >  >   - Jumbo frame support.
>  >  >   - WOL support.
>  >  >
>  >  > As I said, I already know poor performance issue of age(4) but I'm
>  >  > more interested in getting a stable driver. If you're owner of L1
>  >  > gigabit ethernet controller please give it spin and let me know
>  >  > how it goes on your system.
>  >  >
>  >  > Install:
>  >  > o Get age(4) jumbo diff at the following URL. The diff was
>  >  >   generated against HEAD but I guess it would also apply to RELENG_7
>  >  >   and 7.0-RELEASE.
>  >  >   http://people.freebsd.org/~yongari/age/age.HEAD.diff
>  >
>  > For 7.0-RELEASE, use the following URL.
>  > http://people.freebsd.org/~yongari/age/age.7.0R.diff
>  >
>
> It seems that previous version have a bug in getting ethernet
> hardware address. To diagnose it I've updated age(4) again and
> put updated files to the same URL.
>
> For CURRENT:
> http://people.freebsd.org/~yongari/age/age.HEAD.diff
> For RELENG_7/7.0-RELEASE:
> http://people.freebsd.org/~yongari/age/age.7.0R.diff
>
>  >  > o Patch kernel srouce and rebuild/reboot your kernel.
>  >  >   #cd /usr/src
>  >  >   #patch -p0 < /path/to/age.HEAD.diff
>  >  >
>  >  > Test:
>  >  > Use age(4) for your normal network activities and report success or
>  >  > any issues you've encountered. The driver may be chatty to ease of
>  >  > debugging.
>  >  >

I cant get it to work. When I first applied the patch and rebooted the
system the age0 came up in ifconfig. I could apply IP and such, but no
packets went through. I rebooted the system and now I get this in dmesg.

# dmesg | grep age0
age0: <Attansic Technology Corp, L1 Gigabit Ethernet> mem
0xfeac0000-0xfeafffff irq 19 at device 0.0 on pci3
age0: Reserved 0x40000 bytes for rid 0x10 type 3 at 0xfeac0000
age0: PCI device revision : 0x00b0
age0: Chip id/revision : 0xffff
age0: -1 Tx FIFO, -1 Rx FIFO
age0: invalid chip revision : 0x00b0 -- not initialized?

# pciconf -l -v | grep -A4 age0
age0_at_pci0:3:0:0:        class=0x020000 card=0x82261043 chip=0x10481969
rev=0xb0 hdr=0x00
    vendor     = 'Attansic (Now owned by Atheros)'
    device     = 'L1 Gigabit Ethernet 10/100/1000Base-T Ethernet
Controller'
    class      = network
    subclass   = ethernet

The system is Asus P2-M2A690G - Socket AM2 (Barebone)

http://www.asus.com.tw/products.aspx?l1=1&l2=3&l3=483&l4=0&model=1797&modelmenu=1

# uname -a
FreeBSD gw.qvq.se 7.0-STABLE FreeBSD 7.0-STABLE #1: Tue Apr 29 19:26:43
CEST 2008     root_at_gw.qvq.se:/usr/obj/usr/src/sys/GENERIC  i386

One other thing is that the system coredumps at reboot. Which it didnt
happened before I applied the patch.

/Bjorn