Re: tg3 broken on 2.6.17-rc5-mm3

["Michael Chan" <mchan@broadcom.com>]

On Wed, 2006-06-07 at 17:11 -0600, Bjorn Helgaas wrote:
> Something changed between 2.6.17-rc5-mm2 and -mm3 that broke tg3
> on my HP DL360:
> 
> 2.6.17-rc5-mm2:
>   tg3.c:v3.59 (May 26, 2006)
>   ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 30 (level, low) -> IRQ 177
>   eth0: Tigon3 [partno(N/A) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:0e:7f:b4:69:94
>   eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] 
>   eth0: dma_rwctrl[769f4000] dma_mask[64-bit]
> 
> 2.6.17-rc5-mm3 (with a bit of debug showing tg3_read_mem result):
>   tg3.c:v3.59 (May 26, 2006)
>   ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 30 (level, low) -> IRQ 177
>   tg3_get_eeprom_hw_cfg:
>   tg3_get_eeprom_hw_cfg: val 0xffffffff (magic 0x4b657654)
>   tg3_phy_probe: after readphy, err -16 hw_phy_id 0x0
>   tg3_phy_probe: phy_id 0xffffffff
>   lookup_by_subsys: vendor 0xe11 dev 0xcb
>   tg3: (0000:01:02.0) phy probe failed, err -19
>   tg3: Problem fetching invariants of chip, aborting.

My suspicion is that either the memory enable bit in PCI config register
4 is not set or the power state in PCI config register 0x4c is D3hot.
Any of these conditions will cause MMIO registers to return 0xffffffff.

Try reading config registers 0x4 and 0x4c to see what the values are.

Thanks.