Home » Mailing list archives » linux-netdev » 2010 » September » 21

RE: REGRESSION: e1000e fails to communicate in 2.6.36-rcx (82566DM)

Previous thread: stack trace from sctp_getsockopt_local_addrs() by Dan Carpenter on Monday, September 6, 2010 - 12:59 pm. (1 message)

Next thread: [PATCH net-next-2.6] net: poll() optimizations by Eric Dumazet on Monday, September 6, 2010 - 2:13 pm. (2 messages)
[view original message]
From: Priit Laes
Subject: REGRESSION: e1000e fails to communicate (82566DM)
Date: Monday, September 6, 2010 - 1:51 pm

Heya!

After trying out newer 2.6.35-rc3 kernel, the network interface fails to
communicate (via dhcp and manual IP setup).

This seems to be a regression since 2.6.34-rc5:

lspci:

00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network Connection (rev 02)
	Subsystem: Intel Corporation Device 0001
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 31
	Region 0: Memory at 90300000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at 90324000 (32-bit, non-prefetchable) [size=4K]
	Region 2: I/O ports at 20e0 [size=32]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee0300c  Data: 41c9
	Kernel driver in use: e1000e

ethtool:
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Speed: 100Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: off
	Supports Wake-on: pumbag
	Wake-on: g
	Current message level: 0x00000001 (1)
			       drv
	Link detected: yes

--


[ message continues ]
[view original message]
From: Tantilov, Emil S
Subject: RE: REGRESSION: e1000e fails to communicate (82566DM)
Date: Thursday, September 9, 2010 - 10:51 am

Is this still an issue in the latest net-next pull?

Also please provide the output of ethtool -e.

Thanks,
Emil

[ message continues ]
[view original message]
From: Priit Laes
Subject: RE: REGRESSION: e1000e fails to communicate (82566DM)
Date: Friday, September 10, 2010 - 2:57 am

Attached output from 2.6.36-rc3


[ message continues ]
[view original message]
From: Tantilov, Emil S
Subject: RE: REGRESSION: e1000e fails to communicate (82566DM)
Date: Friday, September 10, 2010 - 10:21 am

I think this is a known issue for this device - we have a patch currently 
in test, and we should have it out soon.

Thanks,
Emil

[ message continues ]
[view original message]
From: Priit Laes
Subject: RE: REGRESSION: e1000e fails to communicate in 2.6.36-rcx (82566DM)
Date: Tuesday, September 21, 2010 - 12:26 am

Any news on the patch?

2.6.36-rc5 is already out and I really do not want to see it getting
into major release :(

Cheers,
Priit :)
--


[ message continues ]
[view original message]
From: Tantilov, Emil S
Subject: RE: REGRESSION: e1000e fails to communicate in 2.6.36-rcx (82566DM)
Date: Tuesday, September 21, 2010 - 9:36 am

Thanks,
Emil
[ message continues ]
Previous thread: stack trace from sctp_getsockopt_local_addrs() by Dan Carpenter on Monday, September 6, 2010 - 12:59 pm. (1 message)

Next thread: [PATCH net-next-2.6] net: poll() optimizations by Eric Dumazet on Monday, September 6, 2010 - 2:13 pm. (2 messages)