From: Nix <nix@esperi.org.uk>
To: <jesse.brandeburg@intel.com>
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: Mon, 08 Nov 2010 08:01:29 +0000 [thread overview]
Message-ID: <87wrooi6qu.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <1288837586.2835.3.camel@jbrandeb-mobl2> (Jesse Brandeburg's message of "Wed, 03 Nov 2010 22:26:26 -0400")
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.
It's still rather gruesome that anything like this is even needed, but
as long as it only fires every hour or so I guess I can live with it.
Are there firmware updates or something that might fix this properly in
the end?
next prev parent reply other threads:[~2010-11-08 8:01 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"
2010-11-04 21:35 ` Nix
2010-11-08 8:01 ` Nix [this message]
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=87wrooi6qu.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=e1000-devel@lists.sourceforge.net \
--cc=emil.s.tantilov@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome