> The second thought is that the adapter is in D3, and something about
> your kernel or the driver doesn't successfully wake it up to D0.
On my NICs, the EEPROM ID (Word 0Ah) is set to 0x40a2.
Thus DDPD (bit 6) is set to 0.
DDPD is the "Disable Deep Power Down while PME is disabled" bit.
0 - Deep Power Down is enabled in D3 state while PME-disabled.
1 - Deep Power Down disabled in D3 state while PME-disabled.
This bit should be set to 1b if a TCO controller is being used via the
SMB because it requires receive functionality at all power states.
Are you suggesting I try and set DDPD to 1?
Or is this completely unrelated?
> An indication of this would be looking at lspci -vv before/after
> loading the driver.
$ diff -u lspci_vv_before_e100.txt lspci_vv_after_e100.txt
--- lspci_vv_before_e100.txt 2006-11-09 14:51:30.000000000 +0100
+++ lspci_vv_after_e100.txt 2006-11-09 14:51:30.000000000 +0100
@@ -74,21 +74,20 @@
Expansion ROM at 20000000 [disabled] [size=1M]
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=2 PME-
+ Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
Subsystem: Intel Corporation EtherExpress PRO/100B (TX)
- Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
+ 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-
> Also, after loading/unloading eepro100 does the e100 driver work?
No.
> A third idea is look for a master abort in lspci after e100 fails to
> load.
I don't understand that one.
Attachment:
e100_debug.patch
Description: Binary data