Re: [E1000-devel] problem with e1000 and smp kernel

[Jesse B. <jes...@in...>]

On Mon, 5 Dec 2005, Igor Schein wrote:
> Hi,
> 
> Here's my adapter:
> 
> 01:00.0 Ethernet controller: Intel Corp. 82541GI Gigabit Ethernet Controller
>   Subsystem: Intel Corp. PRO/1000 MT Desktop Adapter
>   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
>   Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR-
> <PERR-
>   Latency: 64 (63750ns min), cache line size 10
>   Interrupt: pin A routed to IRQ 10
>   Region 0: Memory at fe9c0000 (32-bit, non-prefetchable) [size=128K]
>   Region 1: Memory at fe9e0000 (32-bit, non-prefetchable) [size=128K]
>   Region 2: I/O ports at df40 [size=64]
>   Expansion ROM at fea00000 [disabled] [size=128K]
>   Capabilities: [dc] Power Management version 2
>    Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>    Status: D0 PME-Enable- DSel=0 DScale=1 PME-
>   Capabilities: [e4] PCI-X non-bridge device.
>    Command: DPERE- ERO+ RBC=0 OST=0
>    Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0,
> RSCEM-   Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
>    Address: 0000000000000000  Data: 0000
> 
> I downloaded e1000-6.2.15.tar.gz and built an RPM from it.  It works
> with 2.4.21-37.EL kernel but doesn't work with 2.4.21-37.ELsmp -
> ethtool -t fails:
> 
> The test result is FAIL
> The test extra info:
> Register test  (offline)         0
> Eeprom test    (offline)         0
> Interrupt test (offline)         4
> Loopback test  (offline)         0
> Link test   (on/offline)         0
>

Hi Igor, please find this code

 		if (!(adapter->test_icr & mask)) {
 			*data = 4;
 			break;
 		}

and change it to this

 		if (!(adapter->test_icr & mask)) {
 			printk("test_icr is: %08X, mask is %08X\n",
 			       adapter->test_icr, mask);
 			*data = 4;
 			break;
 		}

and then send us the output, its likely that there is something wierd with 
one of the interrupt bits.  My guess is your hardware is fine.

also, please send the output of your
cat /proc/interrupts

and maybe attach your dmesg as well

thanks,
   Jesse