On 01/13/2017 04:17 PM, Mason wrote:
> On 13/01/2017 10:20, Zefir Kurtisi wrote:
>> On 01/12/2017 04:16 PM, Mason wrote:
>>> On 12/01/2017 14:05, Mason wrote:
>>>> I'm wondering what are the semantics of calling
>>>> ip link set dev eth0 down
>>>> I was expecting that to somehow instruct the device's ethernet driver
>>>> to shut everything down, have the PHY tell the peer that it's going
>>>> away, maybe even put the PHY in some low-power mode, etc.
>>>> But it doesn't seem to be doing any of that on my HW.
>>>> So what exactly is it supposed to do?
>>>> And on top of that, I am seeing random occurrences of
>>>> nb8800 26000.ethernet eth0: Link is Down
>>>> Sometimes it is printed immediately.
>>>> Sometimes it is printed as soon as I run "ip link set dev eth0 up" (?!)
>>>> Sometimes it is not printed at all.
>>>> I find this erratic behavior very confusing.
>>>> Is it the symptom of some deeper bug?
>>> Here's an example of "Link is Down" printed when I set link up:
>>> At [ 62.750220] I run ip link set dev eth0 down
>>> Then leave the system idle for 10 minutes.
>>> At [ 646.263041] I run ip link set dev eth0 up
>>> At [ 647.364079] it prints "Link is Down"
>>> At [ 649.417434] it prints "Link is Up - 1Gbps/Full - flow control rx/tx"
>>> I think whether I set up the PHY to use interrupts or polling
>>> does have an influence on the weirdness I observe.
>>> AFAICT, changing the interface flags is done in dev_change_flags
>>> which calls __dev_change_flags and __dev_notify_flags
>>> Is one of these supposed to call the device driver through a
>>> callback at some point?
>>> How/when is the phy_state_machine notified of the change in
>>> interface flags?
>> Hm, reminds me of something at my side that I recently fixed with . For
>> me it
>> was pulling the cable got randomly unnoticed at PHY layer - but might be
>> Do you by chance have some component that polls the link states over the
>> interface very often (like once per second)? At my side it was a snmpd agent
>> pro-actively updated the interface states every second and with that 'stole'
>> link change information from the phy link state machine. What you need to
>> have to
>> run in such a failing situation is:
>> 1) an ETH driver that updates link status in ethtool GSET path (e.g. dsa
>> 2) some component that continuously polls states via ethtool GSET
>>  https://patchwork.ozlabs.org/patch/711839/
> Hello Zefir,
> Thanks for the insightful comment.
> This is a minimal buildroot system, with no frills, and not much running.
> There definitely is no SNMP daemon running, but I can't be 100% sure that
> busybox isn't polling the link state once in a while. (It's unlikely.)
> I'm surprised that there are still bugs lurking in the phy state machine,
> I expected this to be a "solved problem", but I suppose power management
> has broken many assumptions that were once safe...
> By the way, I did come across code paths where phy->state was read or
> written without taking the lock. Isn't that never supposed to happen?
The problem is that phydev->read_status() is not meant to be called from outside
the pyh state machine. Some ETH drivers are doing this in the ethtool GSET path,
either by a wrong assumption that they need to have the link status updated
instantly, or because other drivers are are based on copy-pasting others. I
did not find defined rules what ETH drivers are allowed to call and what they
not, so as a result there is a handful of ETH drivers that are doing it wrong.
Florian is going to push the developers to fix the drivers with time.
As for your specific problem: since I fought myself with the PHY/ETH subsystems
over the past months, I might remember something relevant to your issue. Could
give some more info on your setup (PHY driver, opmode (SGMII, RGMII, etc.),