[eepro100] Second eepro100 recognized "Receiver Lock-Up bug", but nothing ge ts done about it....

[Graham Wooden]

Hello all,

I have a HP LT6000 with an on-board Intel Pro 100 NIC and a PCI Intel
EtherExpress NIC.
I am having a problem with the PCI one, eth1.

According to dmesg, for eth0, it's found the receiver bug, and the work
around gets activated.
And for eth1, its say it does exist, and stats enabling work around, but it
doesn't.

Eth1 goes to sleep about 3-4 minutes after I disconnect from the machine.
The only way I can get Eth1 to respond is to have activity on eth0.

Here is the output from 'dmesg':
>  
> eth0: OEM i82557/i82558 10/100 Ethernet at 0xfc91b000, 00:30:6E:02:B8:EA,
> IRQ 18.
>   Board assembly 506495-096, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>   Forcing 100Mbs full-duplex operation.
>   General self-test: passed.
>   Serial sub-system self-test: passed.
>   Internal registers self-test: passed.
>   ROM checksum self-test: passed (0x04f4518b).
>   Receiver lock-up workaround activated.
> 
> eth1: Intel PCI EtherExpress Pro100 at 0xfc91d000, 00:02:B3:0A:E2:37, IRQ
> 21.
>   Receiver lock-up bug exists -- enabling work-around.
>   Board assembly 721383-016, Physical connectors present: RJ45
>   Primary interface chip i82555 PHY #1.
>   Forcing 100Mbs full-duplex operation.
>   General self-test: passed.
>   Serial sub-system self-test: passed.
>   Internal registers self-test: passed.
>   ROM checksum self-test: passed (0x04f4518b).
> 
> You can see above, in the eth0 statement, that "Receiver lock-up
> workaround activated" has been turned on.
But Eth1 does not state that.
>  
> I ran the eepro100 diagnostic program on this box, and finding some
> interesting information:
> 
> Here is what is reported for the on-board NIC:
> 	Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B
> adapter at 0x1800.
> 	Intel EtherExpress Pro 10/100 EEPROM contents:
> 	  Station address 00:30:6E:02:B8:EA.
> 	  Receiver lock-up bug exists. (The driver work-around *is*
> implemented.)
> 	  Board assembly 506495-096, Physical connectors present: RJ45
> 	  Primary interface chip i82555 PHY #1.
> As you can see from above, the work-around is activitated.
> 
> Here is what is reported for the PCI NIC:
> 	Index #2: Found a Intel i82557 (or i82558) EtherExpressPro100B
> adapter at 0x4800.
> 	Intel EtherExpress Pro 10/100 EEPROM contents:
> 	  Station address 00:02:B3:0A:E2:37.
> 	  Board assembly 721383-016, Physical connectors present: RJ45
> 	  Primary interface chip i82555 PHY #1.
> The program is not reporting the Receiver lock-up bug for the PCI NIC. So,
> the driver is not going to perform that routine.
> 
Any ideas on this? Is there a function with in the code to force this
routine to happen?

Thanks! 

> Graham Wooden
> Red Hat Linux Certified Engineer (R.H.C.E.)
> Systems Engineer | Engineering Department
> (678) 365-2849   | gwooden@interland.com
> Interland, Inc.  | www.interland.com
> 
>