All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: Maxime Morin <maxime.morin@vitec.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"thomas.petazzoni@free-electrons.com"
	<thomas.petazzoni@free-electrons.com>
Subject: Re: Problem: net: mvneta: auto-negotiation with disconnected network cable
Date: Thu, 23 Mar 2017 01:03:37 +0300	[thread overview]
Message-ID: <b7737751-b051-b717-a856-3e11c73dd25d@list.ru> (raw)
In-Reply-To: <DB6PR0501MB2712340C8CDC37F3038766AD943C0@DB6PR0501MB2712.eurprd05.prod.outlook.com>

22.03.2017 16:23, Maxime Morin пишет:
> Hi all,
>
> I work on an embedded platform based on the Marvell Armada 88F6707, that is connected to a Marvell Alaska 88E1512 ethernet transceiver. A defect has appeared recently, and it turns out to be a regression on the network part. There is a complete lost of the network when following these steps:
>      1) boot the board with the network cable disconnected
>      2) run the following commands (or equivalent):
>          ip link set eth0 up
>          ip addr add 10.0.0.80/24 dev eth0
>          ethtool -s eth0 autoneg on #this is the command that really breaks the network
In fact, the problem is that this control is
counter-intuitive. It could instead be

ethtool autoneg [on|off|mdio|inband]

with "on" implying "mdio". In that case you would
never notice the change. Unfortunately there seems
to be no way of passing the autoneg mode, so I fused
"on" to "inband"... So, unless I am mistaken, this clearly
needs a rework. But I have really forgot all the details.

      parent reply	other threads:[~2017-03-22 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 13:23 Problem: net: mvneta: auto-negotiation with disconnected network cable Maxime Morin
2017-03-22 21:34 ` Stas Sergeev
2017-03-23 11:30   ` Maxime Morin
2017-03-23 22:08     ` Stas Sergeev
2017-03-24 14:39       ` Maxime Morin
2017-03-24 21:26         ` Stas Sergeev
2017-03-22 22:03 ` Stas Sergeev [this message]

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=b7737751-b051-b717-a856-3e11c73dd25d@list.ru \
    --to=stsp@list.ru \
    --cc=davem@davemloft.net \
    --cc=maxime.morin@vitec.com \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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.