From: Nix <nix@esperi.org.uk>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: [E1000-devel] [in-tree drivers] freezing e1000e in 2.6.31 (SMP only? MSI? PAUSE!)
Date: Tue, 10 Nov 2009 00:08:47 +0000 [thread overview]
Message-ID: <87eio7meb4.fsf_-_@spindle.srvr.nix> (raw)
In-Reply-To: <87ljihnh81.fsf@spindle.srvr.nix> (nix@esperi.org.uk's message of "Sun, 08 Nov 2009 15:55:58 +0000")
On 8 Nov 2009, nix@esperi.org.uk told this:
> On 6 Nov 2009, Emil S. Tantilov verbalised:
>> Also try disabling Tx pause frames:
>> ethtool -A fastnet tx off autoneg off
>
> Trying that now. No freezes yet, but I haven't really given it long
> enough.
I just did a large number of kernel-build-and-installs with frame
pointers over NFS over the errant link. No problems at all.
I think we can say this fixes it (works around it?)
Does this implicate the gigabit switch I'm talking to, or is it a kernel
bug? (It looks like the cheap Realteks at the other ends of this link
don't support pause frames at all: at least ethtool -a gives
-EOPNOTSUPP, but maybe they simply can't be turned off... hm, r8169.c
vaguely suggests that it supports them but can't turn them off without
source hacking.)
next prev parent reply other threads:[~2009-11-10 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 20:21 [in-tree drivers] freezing e1000e in 2.6.31 (SMP only? MSI?) Nix
2009-11-06 23:58 ` [E1000-devel] " Tantilov, Emil S
2009-11-08 15:55 ` Nix
2009-11-10 0:08 ` Nix [this message]
2009-11-10 1:19 ` [E1000-devel] [in-tree drivers] freezing e1000e in 2.6.31 (SMP only? MSI? PAUSE!) Allan, Bruce W
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=87eio7meb4.fsf_-_@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=e1000-devel@lists.sourceforge.net \
--cc=emil.s.tantilov@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