[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <d35f3fd8-da0e-cc47-7c4e-664c0bb14c0e@linux.ibm.com>
Date: Thu, 27 Jun 2019 15:56:04 -0500
From: Thomas Falcon <tlfalcon@...ux.ibm.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
bjking1@...ibm.com, pradeep@...ibm.com, dnbanerg@...ibm.com
Subject: Re: [PATCH net] net/ibmvnic: Report last valid speed and duplex
values to ethtool
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
Powered by blists - more mailing lists