linux-kernel - RE: [E1000-devel] 2.6.36 abrupt total e1000e carrier loss (cured by reboot)

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: <EA929A9653AAE14F841771FB1DE5A13660283A6815@rrsmsx501.amr.corp.intel.com>
Date:	Mon, 8 Nov 2010 11:11:57 -0700
From:	"Tantilov, Emil S" <emil.s.tantilov@...el.com>
To:	Nix <nix@...eri.org.uk>,
	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
CC:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [E1000-devel] 2.6.36 abrupt total e1000e carrier loss (cured by
 reboot)

Nix wrote:
> On 4 Nov 2010, Jesse Brandeburg spake thusly:
>> The above could be responsible for your issue.  If you don't want to
>> disable ASPM system wide, then you could just make sure to run a
>> recent kernel with the ASPM patches, or get our e1000.sf.net e1000e
>> driver and try it, as it will work around the issue whether or not
>> aspm is enabled. 
> 
> For the record, cherry-picking
> ff10e13cd06f3dbe90e9fffc3c2dd2057a116e4b (the periodic
> phy-crash-and-reset check) atop 2.6.36 seems to have fixed it: at
> least, the machine has been up for a day now without trouble. This
> commit doesn't seem to be in Greg's stable-queue yet, but seems like
> a good candidate. 

This patch should have no effect on your issue if it is indeed ASPM related.
The ASPM issue can be intermittent and I have seen systems run for 3-5 days until the failure occurs, so one day doesn't necessarily rule it out.

BTW - what is the exact make/model of your system (dmidecode).

Thanks,
Emil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/