From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753514AbbDPXU3 (ORCPT ); Thu, 16 Apr 2015 19:20:29 -0400 Received: from violet.fr.zoreil.com ([92.243.8.30]:51705 "EHLO violet.fr.zoreil.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752017AbbDPXUV (ORCPT ); Thu, 16 Apr 2015 19:20:21 -0400 Date: Fri, 17 Apr 2015 01:16:19 +0200 From: Francois Romieu To: linux-kernel@vger.kernel.org Cc: richard_hubbe11@lavabit.com Subject: Re: [net:r8169] kernel 4.0.0 double "link down" on boot Message-ID: <20150416231619.GA8267@electric-eye.fr.zoreil.com> References: <20150416110620.466cf666@127> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150416110620.466cf666@127> X-Organisation: Land of Sunshine Inc. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org rh_ : > I see these double "link down" now in 4.0 > > [ 19.927880] r8169 0000:03:00.2 eth0: link down > [ 19.927902] r8169 0000:03:00.2 eth0: link down > [ 22.328888] r8169 0000:03:00.2 eth0: link up > > Everything seems to be working fine. Is this an indicator of a problem? No. > Safe to ignore? Mostly. > If so why? The driver is notified of a link event. It schedules a link check. The link may be back to its original state before the driver notices the change. As long as you don't experience high frequency link events for an extended duration, you should not care. [...] > Does it make sense to check 3.19 ? No. -- Ueimor