Received: by 10.223.176.46 with SMTP id f43csp3340903wra; Mon, 22 Jan 2018 12:25:51 -0800 (PST) X-Google-Smtp-Source: AH8x227SCN4rt/Rp032VSxTA9Wd2cWkeeOY01ypsU+Femu08KwwlP/zqGuRS8h0mPxa1TDi/iZMb X-Received: by 10.36.161.11 with SMTP id y11mr54656ite.11.1516652751002; Mon, 22 Jan 2018 12:25:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516652750; cv=none; d=google.com; s=arc-20160816; b=s5dPD/iM9/4cEkLJSObP9j75lXPS3Za5BmiMtKKPNTFkV4xTbnz+lsh+3E0rRz9b6C suJI870T4u/0wbUkqrjsmMwQLbAKOc3A6j6LDCwIvbUt9g61pwpYuNdoQ9pg5WV4rZeF CTkTGf6FVm02x4geoa2rwoBetoL3y3AGv++X3++gLdPF+4/cdTZq8xi2S/brr4Z03UJA wz2RpONeHbyakyZYpiRXPyT8/zSMRFxD2GfhmNkxTI4ypDD52B11o9plumqo4RWySyw5 UKERMIP1kZARSa59G7KlTqHvoQJfsLuGY/LlN8ary3kv/ELNz1TItPRfAM/mQbXmN5cJ G+Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=4Jrcn1bmh0L8ZSiGvBpZr5bK0zAgK6HJGAjCByPhhmQ=; b=ZebKz+cW2RD3084gBE3UGQuRJDz3/oauOsjdguDhJaNmMNkYgSdoaNqc/m75J64tEr jvpFqzyc/n+9YCaCnQvWitcL7nkzDyy6RWalciGCnEUEMvpw67fVXtOK/0npmzZTMzup up1Iss/Sr1cF+f+KAcPf24q2msvLt4bQlbQ/aGFlyNrn6R7zQK71RoYZDFKnufe3Qnr0 ganREjZbOaxIBohXXaEzRrOKmx1TdK7+AkYR+1dGiP+w+CIVKCR9DGrGy3cXhzcCf0DQ wV8FDErOFAvoCXeNXiKUJ2duEfugK7H3ouzX9QZrELae9dGVBWtsKiQzKpnS4Voo2ZT3 JxPg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r62si6645031itg.35.2018.01.22.12.25.38; Mon, 22 Jan 2018 12:25:50 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751642AbeAVUZS (ORCPT + 99 others); Mon, 22 Jan 2018 15:25:18 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:40294 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751530AbeAVUZP (ORCPT ); Mon, 22 Jan 2018 15:25:15 -0500 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id CD49D13F8C799; Mon, 22 Jan 2018 12:25:14 -0800 (PST) Date: Mon, 22 Jan 2018 15:25:13 -0500 (EST) Message-Id: <20180122.152513.1108868799788445512.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 From: David Miller In-Reply-To: <751079597.1884905.1516121905374@mail.yahoo.com> References: <751079597.1884905.1516121905374.ref@mail.yahoo.com> <751079597.1884905.1516121905374@mail.yahoo.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 22 Jan 2018 12:25:15 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Denis Du Date: Tue, 16 Jan 2018 16:58:25 +0000 (UTC) > From b5902a4dfc709b62b704997ab64f31c9ef69a6db Mon Sep 17 00:00:00 2001 > From: Denis Du > 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 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.