mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "\"Brandeburg, Jesse\"" <jesse.brandeburg@intel.com>
To: Nix <nix@esperi.org.uk>
Cc: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
	"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: Wed, 03 Nov 2010 22:26:26 -0400	[thread overview]
Message-ID: <1288837586.2835.3.camel@jbrandeb-mobl2> (raw)
In-Reply-To: <87zktsskua.fsf@spindle.srvr.nix>

On Mon, 2010-11-01 at 16:08 -0700, Nix wrote:
> 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network
> Connection

> LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
>         ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

This is a problem, L0s and L1 don't work on these adapters, make sure
that the patches to the driver to disable ASPM upon load are in place
and working (by the ASPM value above indicating ASPM Disabled)

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.


Jesse



  reply	other threads:[~2010-11-04  2:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 23:30 Nix
2010-11-01 18:51 ` [E1000-devel] " Tantilov, Emil S
2010-11-01 23:08   ` Nix
2010-11-04  2:26     ` "Brandeburg, Jesse" [this message]
2010-11-04 21:35       ` Nix
2010-11-08  8:01       ` Nix
2010-11-08 18:11         ` Tantilov, Emil S
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=1288837586.2835.3.camel@jbrandeb-mobl2 \
    --to=jesse.brandeburg@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=emil.s.tantilov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®