From: Nix <nix@esperi.org.uk>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@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: Sun, 14 Nov 2010 17:10:02 +0000 [thread overview]
Message-ID: <87k4kfq1at.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <87sjzbin20.fsf@spindle.srvr.nix> (nix@esperi.org.uk's message of "Mon, 08 Nov 2010 20:21:27 +0000")
On 8 Nov 2010, nix@esperi.org.uk stated:
> On 8 Nov 2010, Emil S. Tantilov verbalised:
>
>> Nix wrote:
>>> 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.
>
> Interesting. I just noticed that it was testing for exactly the same
> symptoms as I was observing (registers suddenly filled with 0xff) and
> resetting the card, and thought it might help (plus it's easier than
> installing an out-of-tree module and I'm lazy so I tried it first).
It didn't help. Unfortunately, neither did the upstream e1000e-1.2.17
module. I have now seen this network-dead bug with basic 2.6.36, with
2.6.36 plus the commit named above, and with 2.6.36 plus e1000e-1.2.17.
Any debugging I can do, just drop me a line. I'm really quite used to
rebooting this system now, what with this *and* the NFS rpc.mountd-
imploding-on-bootup bug biting simultaneously.
prev parent reply other threads:[~2010-11-14 17:10 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
2010-11-08 20:21 ` Nix
2010-11-14 17:10 ` Nix [this message]
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=87k4kfq1at.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 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.