linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Falcon <tlfalcon@linux.ibm.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	bjking1@us.ibm.com, dnbanerg@us.ibm.com
Subject: Re: [PATCH net] net/ibmvnic: Report last valid speed and duplex values to ethtool
Date: Thu, 27 Jun 2019 15:56:04 -0500	[thread overview]
Message-ID: <d35f3fd8-da0e-cc47-7c4e-664c0bb14c0e@linux.ibm.com> (raw)
In-Reply-To: <20190627175715.GP27733@lunn.ch>


On 6/27/19 12:57 PM, Andrew Lunn wrote:
> On Thu, Jun 27, 2019 at 12:09:13PM -0500, Thomas Falcon wrote:
>> This patch resolves an issue with sensitive bonding modes
>> that require valid speed and duplex settings to function
>> properly. Currently, the adapter will report that device
>> speed and duplex is unknown if the communication link
>> with firmware is unavailable.
> Dumb question. If you cannot communicate with the firmware, isn't the
> device FUBAR? So setting the LACP port to disabled is the correct
> things to do.
>
>         Andrew
>
Yes, I think that is correct too.  The problem is that the link is only 
down temporarily.  In this case - we are testing with a pseries logical 
partition - the partition is migrated to another server. The driver must 
wait for a signal from the hypervisor to resume operation with the new 
device.  Once it resumes, we see that the device reboots and gets 
correct speed settings, but the port flag (AD_LACP_PORT_ENABLED) is 
still cleared.

Tom


  reply	other threads:[~2019-06-27 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 17:09 [PATCH net] net/ibmvnic: Report last valid speed and duplex values to ethtool Thomas Falcon
2019-06-27 17:57 ` Andrew Lunn
2019-06-27 20:56   ` Thomas Falcon [this message]
2019-07-02 21:01 ` David Miller

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=d35f3fd8-da0e-cc47-7c4e-664c0bb14c0e@linux.ibm.com \
    --to=tlfalcon@linux.ibm.com \
    --cc=andrew@lunn.ch \
    --cc=bjking1@us.ibm.com \
    --cc=dnbanerg@us.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).