Andrew Morton wrote:
The e1000 changes which popped up in Jeff's netdev tree today break the
driver on my emt64 box. There's no real sign of damage apart from the fact
that it simply won't send stuff.
e1000: 0000:01:02.0: e1000_probe: (PCI:33MHz:32-bit) 00:0e:0c:2f:2c:c1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
01:02.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller
Subsystem: Intel Corp.: Unknown device 3408
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 17
Region 0: Memory at fa3e0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fa3c0000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at cc80 [size=64]
Expansion ROM at 88000000 [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=2, DMOST=0, DMCRS=0, RSCEM-
00: 86 80 76 10 17 01 30 02 00 00 00 02 10 40 00 00
10: 00 00 3e fa 00 00 3c fa 81 cc 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 08 34
30: 00 00 3a fa dc 00 00 00 00 00 00 00 05 01 ff 00
Reverting all the e1000 changes from Jeff's tree fixes it up.
Any chance you could git bisect?
I thought I smelled an e1000 problem here too... I'll look into it
tomorrow.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
