linux-kernel - RE: No link on e1000e with 2.6.35.3 and ThinkPad T60

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <EA929A9653AAE14F841771FB1DE5A136600821444B@rrsmsx501.amr.corp.intel.com>
Date:	Wed, 25 Aug 2010 12:01:40 -0600
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Marc Haber <mh+linux-kernel@...schlus.de>,
	Linux Kernel Developers <linux-kernel@...r.kernel.org>,
	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>
Subject: RE: No link on e1000e with 2.6.35.3 and ThinkPad T60

Marc Haber wrote:
> Hi,
> 
> On Sat, Jul 24, 2010 at 11:26:44AM +0200, Marc Haber wrote:
>> Additionally, sometimes, probably after suspend/resume, the wired
>> ethernet does not come up properly again, ip addr claims "NO CARRIER"
>> even if the LEDs on the interface and on the switch claim that there
>> was a link. No packets are received by the interface when it's at
>> this stage.
> 
> As of 2.6.35.3, this issue has become worse. It now even happens
> directly after freshly booting the system that I cannot get a link on
> the wired ethernet.
> 
> What information do you need to find out what's going on there?

Can you please post the output of dmidecode?

We have a tool that you can use to dump the registers from the port in the failed state:
http://sourceforge.net/projects/e1000/files/Ethregs%20-%20Register%20Dump%20Tool/ethregs-1.12.3/

I have not been able to reproduce any of the issues you reported on T60 here in the lab, so we need to start looking into more details.

Also, could you please file a bug at e1000.sf.net with all the information you provided so far?

Thanks,
Emil