Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756078AbdLORam convert rfc822-to-8bit (ORCPT ); Fri, 15 Dec 2017 12:30:42 -0500 Received: from mga02.intel.com ([134.134.136.20]:39755 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755972AbdLORai (ORCPT ); Fri, 15 Dec 2017 12:30:38 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,405,1508828400"; d="scan'208";a="12626729" From: "Keller, Jacob E" To: "Keller, Jacob E" , Gabriel C , Pavel Machek , kernel list CC: "netdev@vger.kernel.org" , "intel-wired-lan@lists.osuosl.org" Subject: RE: v4.15-rc2 on thinkpad x60: ethernet stopped working Thread-Topic: v4.15-rc2 on thinkpad x60: ethernet stopped working Thread-Index: AQHTcZKBbrzm5NpEY0Sfu2VIaJwRT6M9DB8AgAekryCAAAC2oA== Date: Fri, 15 Dec 2017 17:30:37 +0000 Message-ID: <02874ECE860811409154E81DA85FBB5882B5FB49@ORSMSX115.amr.corp.intel.com> References: <20171210083949.GA3872@amd> <02874ECE860811409154E81DA85FBB5882B5FB2A@ORSMSX115.amr.corp.intel.com> In-Reply-To: <02874ECE860811409154E81DA85FBB5882B5FB2A@ORSMSX115.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjNjZDczNmItOTIzYi00MTU5LWFmMzYtMGE2ZjhhMzU4YTA0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlwvcTBVczVSeVNBNmxmNUFhNTdzN3QwaGJ4SWVzWnVaRUVXbUNIZFVHeEpRPSJ9 x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2667 Lines: 80 > -----Original Message----- > From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On Behalf Of > Keller, Jacob E > Sent: Friday, December 15, 2017 9:29 AM > To: Gabriel C ; Pavel Machek ; kernel list > > Cc: netdev@vger.kernel.org; intel-wired-lan@lists.osuosl.org > Subject: Re: [Intel-wired-lan] v4.15-rc2 on thinkpad x60: ethernet stopped > working > > > -----Original Message----- > > From: netdev-owner@vger.kernel.org [mailto:netdev- > owner@vger.kernel.org] > > On Behalf Of Gabriel C > > Sent: Sunday, December 10, 2017 4:44 AM > > To: Pavel Machek ; kernel list > > Cc: Kirsher, Jeffrey T ; intel-wired- > > lan@lists.osuosl.org; netdev@vger.kernel.org > > Subject: Re: v4.15-rc2 on thinkpad x60: ethernet stopped working > > > > On 10.12.2017 09:39, Pavel Machek wrote: > > > Hi! > > > > Hi, > > > > > In v4.15-rc2+, network manager can not see my ethernet card, and > > > manual attempts to ifconfig it up did not really help, either. > > > > > > Card is: > > > > > > 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet > > > Controller > > > > > > Dmesg says: > > > > > > dmesg | grep eth > > > [ 0.648931] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width > > > x1) 00:16:d3:25:19:04 > > > [ 0.648934] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network > > > Connection > > > [ 0.649012] e1000e 0000:02:00.0 eth0: MAC: 2, PHY: 2, PBA No: > > > 005302-003 > > > [ 0.706510] usbcore: registered new interface driver cdc_ether > > > [ 6.557022] e1000e 0000:02:00.0 eth1: renamed from eth0 > > > [ 6.577554] systemd-udevd[2363]: renamed network interface eth0 to > > > eth1 > > > > > > Any ideas ? > > > > Yes , 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 broke it. > > > > See: > > https://bugzilla.kernel.org/show_bug.cgi?id=198047 > > > > Fix there : > > https://marc.info/?l=linux-kernel&m=151272209903675&w=2 > > > > Regards, > > > > Gabriel C > > Hi, > > Digging into this, the problem is complicated. The original bug assumed behavior > of the .check_for_link call, which is universally not implemented. > > I think the correct fix is to revert 19110cfbb34d ("e1000e: Separate signaling for > link check/link up", 2017-10-10) and find a more proper solution. > > I don't think any other code which uses check_for_link expects the interface to > return in the way this patch attempted. > > Thanks, > Jake > Alternatively, we can go a step farther and make sure every implementation of .check_for_link follows the modified interface. Thanks, Jake