All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
To: Nix <nix@esperi.org.uk>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: "e1000-devel@lists.sourceforge.net" 
	<e1000-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [E1000-devel] 2.6.36 abrupt total e1000e carrier loss (cured by reboot)
Date: Mon, 8 Nov 2010 11:11:57 -0700	[thread overview]
Message-ID: <EA929A9653AAE14F841771FB1DE5A13660283A6815@rrsmsx501.amr.corp.intel.com> (raw)
In-Reply-To: <87wrooi6qu.fsf@spindle.srvr.nix>

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

  reply	other threads:[~2010-11-08 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 23:30 2.6.36 abrupt total e1000e carrier loss (cured by reboot) Nix
2010-11-01 18:51 ` [E1000-devel] " Tantilov, Emil S
2010-11-01 23:08   ` Nix
2010-11-04  2:26     ` "Brandeburg, Jesse"
2010-11-04 21:35       ` Nix
2010-11-08  8:01       ` Nix
2010-11-08 18:11         ` Tantilov, Emil S [this message]
2010-11-08 20:21           ` Nix
2010-11-14 17:10             ` Nix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EA929A9653AAE14F841771FB1DE5A13660283A6815@rrsmsx501.amr.corp.intel.com \
    --to=emil.s.tantilov@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.