From: David Miller <davem@davemloft.net>
To: dudenis2000@yahoo.ca
Cc: khc@pm.waw.pl, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Carrier detect ok, don't turn off negotiation
Date: Mon, 22 Jan 2018 15:25:13 -0500 (EST) [thread overview]
Message-ID: <20180122.152513.1108868799788445512.davem@davemloft.net> (raw)
In-Reply-To: <751079597.1884905.1516121905374@mail.yahoo.com>
From: Denis Du <dudenis2000@yahoo.ca>
Date: Tue, 16 Jan 2018 16:58:25 +0000 (UTC)
> From b5902a4dfc709b62b704997ab64f31c9ef69a6db Mon Sep 17 00:00:00 2001
> From: Denis Du <dudenis2000@yahoo.ca>
> Date: Mon, 15 Jan 2018 17:26:06 -0500
> Subject: [PATCH] netdev: carrier detect ok, don't turn off negotiation
>
> Sometimes when physical lines have a just good noise to make the protocol
> handshaking fail, but the carrier detect still good. Then after remove of
> the noise, nobody will trigger this protocol to be start again to cause
> the link to never come back. The fix is when the carrier is still on, not
> terminate the protocol handshaking.
>
> Signed-off-by: Denis Du <dudenis2000@yahoo.ca>
The timer is supposed to restart the protocol again, that's how this
whole thing is designed to work.
I think you are making changes to the symptom rather than the true
cause of the problems you are seeing.
Sorry, I will not apply this until the exact issue is better
understood.
Thank you.
next prev parent reply other threads:[~2018-01-22 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <751079597.1884905.1516121905374.ref@mail.yahoo.com>
2018-01-16 16:58 ` Denis Du
2018-01-22 20:25 ` David Miller [this message]
2018-01-22 22:17 ` Denis Du
2018-01-23 17:08 ` Denis Du
2018-01-28 14:24 ` Krzysztof Halasa
2018-02-06 15:18 ` Denis Du
[not found] ` <438911112.3985245.1517930128335@mail.yahoo.com>
2018-02-06 15:29 ` David Miller
2018-02-06 16:50 ` Denis Du
2018-02-21 3:35 ` Denis Du
2018-02-22 19:04 ` David Miller
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=20180122.152513.1108868799788445512.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dudenis2000@yahoo.ca \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®