From: Mason <slash.tmp@free.fr>
To: netdev <netdev@vger.kernel.org>
Cc: Mans Rullgard <mans@mansr.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>
Subject: Re: Setting link down or up in software
Date: Thu, 12 Jan 2017 16:16:49 +0100 [thread overview]
Message-ID: <2044a26f-cf95-ac55-6265-ac76c3ca53f6@free.fr> (raw)
In-Reply-To: <75bd6df2-714a-2b9b-a0e3-f5574c295377@free.fr>
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?
Regards.
next prev parent reply other threads:[~2017-01-12 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:05 Setting link down or up in software Mason
2017-01-12 15:16 ` Mason [this message]
2017-01-12 15:28 ` Andrew Lunn
2017-01-12 16:22 ` Mason
2017-01-12 16:27 ` Andrew Lunn
2017-01-12 18:45 ` Dan Williams
2017-01-13 9:20 ` Zefir Kurtisi
2017-01-13 15:17 ` Mason
2017-01-13 16:28 ` Zefir Kurtisi
2017-01-13 17:35 ` Mason
2017-01-18 10:29 ` Zefir Kurtisi
2017-01-19 15:40 ` Mason
2017-01-19 17:56 ` Måns Rullgård
2017-01-19 17:59 ` Florian Fainelli
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=2044a26f-cf95-ac55-6265-ac76c3ca53f6@free.fr \
--to=slash.tmp@free.fr \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=thibaud_cornic@sigmadesigns.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.