From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gospo@cumulusnetworks.com" <gospo@cumulusnetworks.com>,
zhuyj <zyjzyj2000@gmail.com>,
"jiri@mellanox.com" <jiri@mellanox.com>
Subject: Re: bonding reports interface up with 0 Mbps
Date: Thu, 04 Feb 2016 12:29:33 -0800 [thread overview]
Message-ID: <22896.1454617773@famine> (raw)
In-Reply-To: <87618083B2453E4A8714035B62D6799250524233@FMSMSX105.amr.corp.intel.com>
Tantilov, Emil S <emil.s.tantilov@intel.com> wrote:
>We are seeing an occasional issue where the bonding driver may report interface up with 0 Mbps:
>bond0: link status definitely up for interface eth0, 0 Mbps full duplex
>
>So far in all the failed traces I have collected this happens on NETDEV_CHANGELOWERSTATE event:
>
><...>-20533 [000] .... 81811.041241: ixgbe_service_task: eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX
><...>-20533 [000] .... 81811.041257: ixgbe_check_vf_rate_limit <-ixgbe_service_task
><...>-20533 [000] .... 81811.041272: ixgbe_ping_all_vfs <-ixgbe_service_task
>kworker/u48:0-7503 [010] .... 81811.041345: ixgbe_get_stats64 <-dev_get_stats
>kworker/u48:0-7503 [010] .... 81811.041393: bond_netdev_event: eth1: event: 1b
>kworker/u48:0-7503 [010] .... 81811.041394: bond_netdev_event: eth1: IFF_SLAVE
>kworker/u48:0-7503 [010] .... 81811.041395: bond_netdev_event: eth1: slave->speed = ffffffff
><...>-20533 [000] .... 81811.041407: ixgbe_ptp_overflow_check <-ixgbe_service_task
>kworker/u48:0-7503 [010] .... 81811.041407: bond_mii_monitor: bond0: link status definitely up for interface eth1, 0 Mbps full duplex
Thinking about the trace again... Emil: what happens in the
trace before this? Is there ever a call to the ixgbe_get_settings?
Does a NETDEV_UP or NETDEV_CHANGE event ever hit the bond_netdev_event
function?
Could you describe your test that reproduces this? I'd like to
see if I can set it up locally.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2016-02-04 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 23:10 bonding reports interface up with 0 Mbps Tantilov, Emil S
2016-02-04 2:56 ` zhuyj
2016-02-04 5:57 ` Jay Vosburgh
2016-02-04 6:44 ` zhuyj
2016-02-04 15:47 ` Tantilov, Emil S
2016-02-04 20:19 ` Jay Vosburgh
2016-02-04 20:29 ` Jay Vosburgh [this message]
2016-02-05 0:07 ` Tantilov, Emil S
2016-02-05 0:37 ` Jay Vosburgh
2016-02-05 0:43 ` Tantilov, Emil S
2016-02-05 5:19 ` zhuyj
2016-02-05 3:24 ` zhuyj
2016-02-05 16:43 ` Tantilov, Emil S
2016-02-08 16:30 ` Tantilov, Emil S
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=22896.1454617773@famine \
--to=jay.vosburgh@canonical.com \
--cc=emil.s.tantilov@intel.com \
--cc=gospo@cumulusnetworks.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=zyjzyj2000@gmail.com \
/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.