From: Mason <slash.tmp@free.fr>
To: netdev <netdev@vger.kernel.org>
Cc: Mans Rullgard <mans@mansr.com>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>,
Thomas Gambier <thomas_gambier@sigmadesigns.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: Setting link down hangs the kernel
Date: Tue, 10 Jan 2017 16:28:05 +0100 [thread overview]
Message-ID: <b478607d-cb69-0efc-5a8c-9b7a54b88d68@free.fr> (raw)
In-Reply-To: <3ac03634-02fa-6acd-479d-fc475fc45736@free.fr>
On 10/01/2017 15:36, Mason wrote:
> I'm using kernel v4.9 on a [new] dev board.
> I built a small kernel + rootfs with buildroot 2016.11.1
> eth0 is driven by drivers/net/ethernet/aurora/nb8800.c
>
> After booting, I just run udhcpc (busybox version)
> Then I set the link down, and the kernel hangs.
So far, I've been unable to reproduce this issue on an older
smp8758 dev board.
# while true
> do
> ip link set dev eth0 down
> sleep 3
> ip link set dev eth0 up
> sleep 3
> let "++XX"
> echo $XX
> done
The output is strange nonetheless:
1
2
3
4
5
[ 179.002757] nb8800 26000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
6
7
[ 192.538648] nb8800 26000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
8
9
10
11
12
[ 222.284936] nb8800 26000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
13
14
^C
# [ 235.800851] nb8800 26000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
A) I would expect a "Link is Up" message for every "link up" command.
I get only 4 messages for 14 commands. Is that expected?
B) Twice, the PHY was only able to negotiate 100 Mbps, although the
peer supports 1 Gbps. What could cause this?
Regards.
next prev parent reply other threads:[~2017-01-10 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:36 Setting link down hangs the kernel Mason
2017-01-10 15:28 ` Mason [this message]
2017-01-10 17:29 ` Mason
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=b478607d-cb69-0efc-5a8c-9b7a54b88d68@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 \
--cc=thomas_gambier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox