Strange Netgear GA620T

[Jason Thorpe]

Hey folks...

I recently picked up a Netgear GA620T because I wanted a board supported buy the "ti" driver for testing. Plopped it into my test mule and I was surprised with this:

[ 1.0000000] vendor 1385 product 610a (miscellaneous prehistoric, revision 0x01) at pci0 dev 10 function 0 not configured

The valid PCI product IDs for the GA620 family are 0x620a and 0x630a. So, I decided, what the heck, let's make it match 0x610a too!

[ 1.0000000] ti0 at pci0 dev 10 function 0: Netgear GA620 1000BASE-T Ethernet (rev. 0x01)
[ 1.0000000] ti0: interrupting at irq 9
[ 1.0000000] ti0: unsupported chip revision 0x80000000
[ 1.0000000] ti0: chip initialization failed

Huh!

Tigon I chip rev is 0x40000000, Tigon II chip rev is 0x60000000.

I'm a little confused... the board is very clearly labeled "NETGEAR GA620T Rev. A". Linux was no help, they don't seem to have a driver that matches this product ID, either.

What the heck do I have??

-- thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[SAITOH Masanobu]

Post by Jason Thorpe
Hey folks...
[ 1.0000000] vendor 1385 product 610a (miscellaneous prehistoric, revision 0x01) at pci0 dev 10 function 0 not configured
The valid PCI product IDs for the GA620 family are 0x620a and 0x630a. So, I decided, what the heck, let's make it match 0x610a too!
[ 1.0000000] ti0 at pci0 dev 10 function 0: Netgear GA620 1000BASE-T Ethernet (rev. 0x01)
[ 1.0000000] ti0: interrupting at irq 9
[ 1.0000000] ti0: unsupported chip revision 0x80000000
[ 1.0000000] ti0: chip initialization failed
Huh!
Tigon I chip rev is 0x40000000, Tigon II chip rev is 0x60000000.
I'm a little confused... the board is very clearly labeled "NETGEAR GA620T Rev. A". Linux was no help, they don't seem to have a driver that matches this product ID, either.
What the heck do I have??
-- thorpej

The following output of pcictl is form my GA620T Rev. A.
If it has big difference between mine and yours, your card
might be broken (because of broken ROM image or the data bus
is unstable).

PCI configuration registers:
Common header:
0x00: 0x630a1385 0x02a00006 0x02000001 0x00004010

Vendor Name: Netgear (0x1385)
Device Name: GA620 1000baseT Ethernet (0x630a)
Command register: 0x0006
I/O space accesses: off
Memory space accesses: on
Bus mastering: on
Special cycles: off
MWI transactions: off
Palette snooping: off
Parity error checking: off
Address/data stepping: off
System error (SERR): off
Fast back-to-back transactions: off
Interrupt disable: off
Status register: 0x02a0
Immediate Readiness: off
Interrupt status: inactive
Capability List support: off
66 MHz capable: on
User Definable Features (UDF) support: off
Fast back-to-back capable: on
Data parity error detected: off
DEVSEL timing: medium (0x1)
Slave signaled Target Abort: off
Master received Target Abort: off
Master received Master Abort: off
Asserted System Error (SERR): off
Parity error detected: off
Class Name: network (0x02)
Subclass Name: ethernet (0x00)
Interface: 0x00
Revision ID: 0x01
BIST: 0x00
Header Type: 0x00 (0x00)
Latency Timer: 0x40
Cache Line Size: 64bytes (0x10)

Type 0 ("normal" device) header:
0x10: 0xf7200000 0x00000000 0x00000000 0x00000000
0x20: 0x00000000 0x00000000 0x00000000 0x630a1385
0x30: 0x00000000 0x00000000 0x00000000 0x0040010a

Base address register at 0x10
type: 32-bit nonprefetchable memory
base: 0xf7200000
Base address register at 0x14
not implemented
Base address register at 0x18
not implemented
Base address register at 0x1c
not implemented
Base address register at 0x20
not implemented
Base address register at 0x24
not implemented
Cardbus CIS Pointer: 0x00000000
Subsystem vendor ID: 0x1385
Subsystem ID: 0x630a
Expansion ROM Base Address Register: 0x00000000
base: 0x00000000
Expansion ROM Enable: off
Validation Status: Validation not supported
Validation Details: 0x0
Reserved @ 0x34: 0x00000000
Reserved @ 0x38: 0x00000000
Maximum Latency: 0x00
Minimum Grant: 0x40
Interrupt pin: 0x01 (pin A)
Interrupt line: 0x0a

Device-dependent header:
0x40: 0x60000020 0x00c03200 0x00000000 0x00000000
0x50: 0x03100000 0xc8097750 0x00000000 0x760aff00
0x60: 0x10460000 0x00000001 0x000ff800 0x00000000
0x70: 0x10460000 0x00000001 0x00000000 0x00000000
0x80: 0x00000000 0x00000000 0x00000000 0x00000000
0x90: 0x00000000 0x00000000 0x00000000 0x00000000
0xa0: 0x00000080 0x00000000 0x00000000 0x00000000
0xb0: 0x0001f080 0x00000000 0x00000000 0x00000000
0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
0xe0: 0x001fe000 0x001fe000 0x001fe000 0xffffff00
0xf0: 0x001fd800 0x001fd800 0x001fd800 0x001fd800

[Jason Thorpe]

THREAD BUMP!

Post by SAITOH Masanobu
The following output of pcictl is form my GA620T Rev. A.
If it has big difference between mine and yours, your card
might be broken (because of broken ROM image or the data bus
is unstable).

I picked up an IBM-branded flavor of this device which seems to work correctly:

cobalt# pcictl pci0 dump -d 10
PCI configuration registers:
Common header:
0x00: 0x000212ae 0x82a00306 0x02000001 0x0000f808

Vendor Name: Alteon (0x12ae)
Device Name: ACEnic 1000baseT Ethernet (0x0002)
Command register: 0x0306
I/O space accesses: off
Memory space accesses: on
Bus mastering: on
Special cycles: off
MWI transactions: off
Palette snooping: off
Parity error checking: off
Address/data stepping: off
System error (SERR): on
Fast back-to-back transactions: on
Interrupt disable: off
Status register: 0x82a0
Immediate Readiness: off
Interrupt status: inactive
Capability List support: off
66 MHz capable: on
User Definable Features (UDF) support: off
Fast back-to-back capable: on
Data parity error detected: off
DEVSEL timing: medium (0x1)
Slave signaled Target Abort: off
Master received Target Abort: off
Master received Master Abort: off
Asserted System Error (SERR): off
Parity error detected: on
Class Name: network (0x02)
Subclass Name: ethernet (0x00)
Interface: 0x00
Revision ID: 0x01
BIST: 0x00
Header Type: 0x00 (0x00)
Latency Timer: 0xf8
Cache Line Size: 32bytes (0x08)

Type 0 ("normal" device) header:
0x10: 0x12080000 0x00000000 0x00000000 0x00000000
0x20: 0x00000000 0x00000000 0x00000000 0x000212ae
0x30: 0x00000000 0x00000000 0x00000000 0x00400109

Base address register at 0x10
type: 32-bit nonprefetchable memory
base: 0x12080000
Base address register at 0x14
not implemented
Base address register at 0x18
not implemented
Base address register at 0x1c
not implemented
Base address register at 0x20
not implemented
Base address register at 0x24
not implemented
Cardbus CIS Pointer: 0x00000000
Subsystem vendor ID: 0x12ae
Subsystem ID: 0x0002
Expansion ROM Base Address Register: 0x00000000
base: 0x00000000
Expansion ROM Enable: off
Validation Status: Validation not supported
Validation Details: 0x0
Reserved @ 0x34: 0x00000000
Reserved @ 0x38: 0x00000000
Maximum Latency: 0x00
Minimum Grant: 0x40
Interrupt pin: 0x01 (pin A)
Interrupt line: 0x09

Device-dependent header:
0x40: 0x60000020 0x00c03260 0x00000000 0x00000000
0x50: 0x00103455 0xba4f808c 0xd6ddeefa 0x7612ff00
0x60: 0x99666b89 0xdbae3ff3 0x000ff800 0x00000000
0x70: 0xb9c7639a 0xdbae3ff3 0x1fd7fb7b 0x000000f5
0x80: 0xeffffdaf 0xfffdfff7 0xeffffdaf 0xfffdfff7
0x90: 0xffffdffb 0xefffc007 0x0001ffe0 0x0001ffe0
0xa0: 0x00000080 0x006b45e9 0x00005fbf 0x0000aff8
0xb0: 0x0001f080 0x007a7bfe 0x00003fd7 0x007a7bfe
0xc0: 0x001d5000 0x00166fc0 0x001bfe58 0x001d7ff8
0xd0: 0x00110000 0x000572a0 0x001d7ba8 0x00000000
0xe0: 0x0010e000 0x0010e000 0x0010e000 0xffffff00
0xf0: 0x0010d800 0x0010d800 0x0010d800 0x0010d800
cobalt#

I guess I will recycle the other one that's busted.

-- thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Jason Thorpe]

If dim memory serves, these cards were originally sold as 64-bit/66MHz PCI devices. The one I examined in a lab actually forced the PCI/PCI-X bus down to 33MHz. (You can check the relevant edge-connectors with a continuity meter.) If your aggregate bus bandwidth nosedives, that's probably why.
I recall it vividly. It was the fastest-escalated support call I've ever had. Except they never called back.

In this case, I'm plugging it into a 33MHz/32-bit slot :-). I'm pretty sure the previous GA620T I had had some sort of hardware fault. In any case, it now means, I can debug the issue that msaitoh@ reported to me, so all is good!

-- thorpej


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de