Received: by 10.223.176.46 with SMTP id f43csp3434536wra; Mon, 22 Jan 2018 14:17:58 -0800 (PST) X-Google-Smtp-Source: AH8x225xPiQgztN5tIxY9goijjdFcBNIHMM28H9LZ0ZxPaZWs/pnQdciObDMd7DaSpP9p8FxllxM X-Received: by 10.36.67.77 with SMTP id s74mr504024itb.149.1516659478155; Mon, 22 Jan 2018 14:17:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516659478; cv=none; d=google.com; s=arc-20160816; b=xdwugYlo5GMnC2OqB+vQFBdsXY1pOJYAIDMCOGnM+UhTzuyaWkSldAhK72eaE7uTsk pwiNu1zs+IkWARkk82K0ddIKpXaCzX5Xc93Kff2aQ0sN7zVLN5Gx18wSIlLNWqgrdODr iNMVqcxUSphwehDzSi9WNe9LVbRvrmM8aMaCEAO1onhkf49Lu9W03L7RNrK/SiFblvmX 8s5aY138RPQsCMl9gT40aOmoZyhBJS3eygxrLQgvfZx+76RPJ2BCn+qWGGhZDO0CFLep M/iA5AFhKWavJd3UIzI/U2qZKrKJl4/p7nu4HA8/ZxNkJ2lDeIS4euc9VSoN5dlYbwW2 50UA== 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 :subject:references:in-reply-to:message-id:cc:to:from:date :dkim-signature:arc-authentication-results; bh=aw0fSD0Z6cMrqdPZpyLcuXq4JotnO/A93UJBdYQl05A=; b=JirAmNpRaK9kzAOdML6bpck5bKnt8YU/REdFfeYJEkBdVN2KG5CosyFFSGPkddOxdL g2bcTVFS9HU9uUKbSBhG2Kp4KhZ8Xnx1J6Qh2Z6arV6H/u31eFnHVS2J/cZc4c3EFGjM 2ssFFdGp19kL0hQbsLb4NI3f22DRoJdOYtJZHnL+I/0Suf4f6pr1QAjBUtLqvrG+EML0 Iad1kB601OP+/Zpufa0v07JefCyzYXiCayhngZpCOo7TJFEtHeo2yeSgtdc5C37bHt2Q mpZddsIa669XNnjFHJQGevlwbnIsy+AINd+rICfb81ZH6CeyQJ1rkjNx7OIfC++X+E+q Vsvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yahoo.ca header.s=s2048 header.b=kSAzBeWM; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=yahoo.ca Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m16si13734370ioe.64.2018.01.22.14.17.44; Mon, 22 Jan 2018 14:17:58 -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; dkim=pass header.i=@yahoo.ca header.s=s2048 header.b=kSAzBeWM; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=yahoo.ca Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751188AbeAVWRM (ORCPT + 99 others); Mon, 22 Jan 2018 17:17:12 -0500 Received: from sonic305-4.consmr.mail.bf2.yahoo.com ([74.6.133.43]:33663 "EHLO sonic305-4.consmr.mail.bf2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751002AbeAVWRL (ORCPT ); Mon, 22 Jan 2018 17:17:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1516659430; bh=aw0fSD0Z6cMrqdPZpyLcuXq4JotnO/A93UJBdYQl05A=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From:Subject; b=kSAzBeWMfzJNqFqxCVkOewjBtjUlO2t0+zKVUKjRtkC2k44FZ5E4Vw5/YgzUCQZCHfGibDr6ir/fSBaCbTQSN7h3czf3gjDAPTPRFo5ZFOQFynQIl0d3QZ0r1Wsgla08O7aUns5YkNh9dG8cO1tvpc/TaKNs5xYsDBhbbOsqLjDXU6rHbZWt6G1v4FLIP/W9s2fHF8PlD0sEy6Z/C2/H6i6UnJx9rK5otdhw9CfueI8u7IjaNPg4RqF+mr94sqNDFJCRTKyWixz6tDlQ6GxaJgauWm/q9pF9L6fDxSZKtcvf5zSgKu24CqMTHU/o40NlfchXfE50LwwpKAICg4fBDQ== X-YMail-OSG: DC_bSrUVM1lgOEKK9YxPNRkveAcvnTZuNv4dMwpFZORVMyWl40PoPW2vj1t0Q2R 3yd6qwhFWU1tN0iWDiGzfheHGKGiUwa9TaOW5fhcyDafYwYI0cF.56qZDnJ4gQRoBwSd0tcnFZ1m 1mSfrcWfFgjZaen9mQ4LzKXHH0nOXHA5MItm4Zze43LPNnAVeKtwPr4ufAiWkHiKuHFFVmtcGKhO dPDt8u8J5hRr2Fayo5jNnqip.OQ.caV1lC_q5fVU6WlGyNTujujBK9uB_YIAAZ_5ylO1BCjkhLZL jKaAq8njG6TZ4cC8FD_BHKCkoAXH9fLxQYv3TjtFED3gjUCSuK8xhzySBCiP4glLwZeF_uI88ZYT fOq8Zi5XettmphWEZvp4Q8dR4f0LWynogLZcv5PgrkDSDJsgzd2HR0Mky3g7pZVgTHN.mu8EjtLv 463FrJkGETOgQWs5adJ40qRju0FXmTwR6S07fTGXLyDI_vtnPODJS0LO9NG5COm4bfPnxP7tGx6u XrrhW4cRSSGVmNkujj8ATS12VSVNRqge2qD.p Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.bf2.yahoo.com with HTTP; Mon, 22 Jan 2018 22:17:10 +0000 Date: Mon, 22 Jan 2018 22:17:06 +0000 (UTC) From: Denis Du To: David Miller Cc: khc@pm.waw.pl, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <1243263981.2842803.1516659426298@mail.yahoo.com> In-Reply-To: <20180122.152513.1108868799788445512.davem@davemloft.net> References: <751079597.1884905.1516121905374.ref@mail.yahoo.com> <751079597.1884905.1516121905374@mail.yahoo.com> <20180122.152513.1108868799788445512.davem@davemloft.net> Subject: Re: [PATCH] Carrier detect ok, don't turn off negotiation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailer: WebService/1.1.11214 YMailNorrin Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Content-Length: 1813 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The timer is supposed to be triggered by carrier detect interrupt. After re= move the line noise, the carrier detect interrupt is never triggered again,= because the carrier is always ok and it only trigger the timer once, Since= the protocol was terminated and no new interrupts happen, the link will ne= ver be back. So the case here is that the line noise is good and just good = to make the carrier detect still good=C2=A0 but the protocol fail, the time= r will be never triggered again. Of course, if you increase the noise and make even the carrier detect fail,= then remove the noise, the link will be up, Because the carrier down and u= p again and then trigger the timer to restart. Denis Du On Monday, January 22, 2018, 3:25:16 PM EST, David Miller wrote:=20 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 >=20 > 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. >=20 > 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.