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  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]
Date:	Thu, 26 Aug 2010 11:22:45 -0600
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Marc Haber <mh+linux-kernel@...schlus.de>
CC:	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

>-----Original Message-----
>From: Marc Haber [mailto:mh+linux-kernel@...schlus.de]
>Sent: Thursday, August 26, 2010 4:28 AM
>To: Tantilov, Emil S
>Cc: Linux Kernel Developers; Linux Kernel Network Developers; e1000-
>devel@...ts.sourceforge.net
>Subject: Re: No link on e1000e with 2.6.35.3 and ThinkPad T60
>
>On Wed, Aug 25, 2010 at 12:01:40PM -0600, Tantilov, Emil S wrote:
>> Marc Haber wrote:
>> > 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?
>
>Attached.
>
>> 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/
>
>Attached, for an interface in the working state. I'll deliver another
>regdump when I see the issue again.
>
>> 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?
>
>Will do in the next days.
>
>I guess it would be better to file two bugs, one for the crashes and
>one for the no-link-in-some-situations issue, right? Or is it likely
>that they both have the same cause?

If you feel like the issues are unrelated then file 2 bugs. 

As far as the crashes go - it would help a lot if you can get a trace.
You can use a serial console if you have a docking station for the T60.

Also make sure to include all the information you provided so far in the bugs.

Thanks,
Emil


Powered by blists - more mailing lists