From: Mason <slash.tmp@free.fr>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Mans Rullgard <mans@mansr.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Zach Brown <zach.brown@ni.com>, Shaohui Xie <shaohui.xie@nxp.com>,
Tim Beale <tim.beale@alliedtelesis.co.nz>,
Brian Hill <brian@houston-radar.com>,
Vince Bridgers <vbridgers2013@gmail.com>,
Balakumaran Kannan <kumaran.4353@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Sebastian Frias <sf84@laposte.net>,
Kirill Kapranov <kapranoff@inbox.ru>
Subject: Re: Debugging Ethernet issues
Date: Sun, 13 Nov 2016 20:51:46 +0100 [thread overview]
Message-ID: <5828C452.6050808@free.fr> (raw)
In-Reply-To: <20161113030919.GA2892@lunn.ch>
On 13/11/2016 04:09, Andrew Lunn wrote:
> Mason wrote:
>
>> When connected to a Gigabit switch
>> 3.4 negotiates a LAN DHCP setup instantly
>> 4.7 requires over 5 seconds to do so
>
> When you run tcpdump on the DHCP server, are you noticing the first
> request is missing?
>
> What can happen is the dhclient gets started immediately and sends out
> its first request before auto-negotiation has finished. So this first packet
> gets lost. The retransmit after a few seconds is then successful.
I will run tcpdump on the server as I run udhcpc on the client
for Linux 3.4 vs 4.7
Do you know what would make auto-negotiation fail at 100 Mbps
on 4.7? (whereas it succeeds on 3.4)
(Thinking out loud) If the problem were in auto-negotiation,
then if should work if I hard-code speed and duplex using
ethtool, right? (IIRC, hard-coding doesn't help.)
Regards.
next prev parent reply other threads:[~2016-11-13 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 0:01 Debugging Ethernet issues Mason
2016-11-13 3:09 ` Andrew Lunn
2016-11-13 19:51 ` Mason [this message]
2016-11-13 19:55 ` Florian Fainelli
2016-11-14 13:03 ` Sebastian Frias
2016-11-14 13:28 ` Mason
2016-11-14 13:34 ` Andrew Lunn
2016-11-14 14:58 ` Mason
2016-11-14 15:33 ` Mason
2016-11-14 17:32 ` Florian Fainelli
2016-11-14 17:59 ` Sebastian Frias
2016-11-14 18:20 ` Florian Fainelli
2016-11-14 18:42 ` Florian Fainelli
2016-11-14 19:00 ` Måns Rullgård
2016-11-14 19:19 ` Florian Fainelli
2016-11-17 22:17 ` Måns Rullgård
2016-11-14 20:27 ` Mason
2016-11-14 21:00 ` Florian Fainelli
2016-11-14 22:48 ` Mason
2016-11-16 11:10 ` Sebastian Frias
2016-11-14 12:13 ` Mason
2016-11-14 12:45 ` 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=5828C452.6050808@free.fr \
--to=slash.tmp@free.fr \
--cc=andrew@lunn.ch \
--cc=brian@houston-radar.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kapranoff@inbox.ru \
--cc=kumaran.4353@gmail.com \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=sf84@laposte.net \
--cc=shaohui.xie@nxp.com \
--cc=thomas.lendacky@amd.com \
--cc=tim.beale@alliedtelesis.co.nz \
--cc=vbridgers2013@gmail.com \
--cc=zach.brown@ni.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.