From: Stephen Hemminger <shemming@brocade.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] stopping 10GC(x540T2) port does not down the link
Date: Fri, 11 Sep 2015 18:24:26 -0700 [thread overview]
Message-ID: <20150911182426.6f69e711@urahara> (raw)
In-Reply-To: <C97FC248-54C0-4458-82EB-ED894C7437F7@intel.com>
On Sat, 12 Sep 2015 00:54:48 +0000
"Rustad, Mark D" <mark.d.rustad@intel.com> wrote:
> Wen Chiu,
>
> > On Sep 11, 2015, at 5:28 PM, Wen Chiu <Wen.Chiu@brocade.com> wrote:
> >
> > Thanks for your prompted response. First of all, let me clarify the issue. The issue was first seen with our vRouter running DPDK. To isolate it, we setup a Ubuntu 13.4 based baremetal box to try the same and the issue was also seen. So, it is now genuine linux (driver?) issue.
>
> Ah. Ok. Can you tell me what the kernel version is on Ubuntu 13.4? I just checked and found that code to control the phy power did not get into the kernel driver until kernel version 4.2.
>
> > I did try what you suggest and used ethtool to see the eth8 status below. Both ports are already set to "d".
> > wen at wen-PowerEdge-R620:~$ sudo ethtool eth8 |grep Wake
> > Supports Wake-on: d
> > Wake-on: d
> > wen at wen-PowerEdge-R620:~$ sudo ethtool eth9 |grep Wake
> > Supports Wake-on: d
> > Wake-on: d
>
> Yup. WOL is disabled.
>
> > After I administratively disable eth8, eth9 (the other end of the connected port) still shows UP. Any other ideas? Please let me know.
>
> As I indicated above, the kernel driver did not get code to control phy power until version 4.2. The out-of-tree Source Forge driver got that code earlier, so it is in the current version posted there. You could try installing that driver and see if it works for you if that is easier than getting to the 4.2 kernel.
Please identify the commit, and tell David Miller (and netdev) to merge that into the stable tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20150911/e99eef3e/attachment-0001.asc>
prev parent reply other threads:[~2015-09-12 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 22:19 [Intel-wired-lan] stopping 10GC(x540T2) port does not down the link Wen Chiu
2015-09-11 16:16 ` Rustad, Mark D
2015-09-12 0:28 ` Wen Chiu
2015-09-12 0:54 ` Rustad, Mark D
2015-09-12 1:24 ` Stephen Hemminger [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=20150911182426.6f69e711@urahara \
--to=shemming@brocade.com \
--cc=intel-wired-lan@osuosl.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;
as well as URLs for NNTP newsgroup(s).