Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932550AbdLOPwS (ORCPT ); Fri, 15 Dec 2017 10:52:18 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:52004 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932247AbdLOPwN (ORCPT ); Fri, 15 Dec 2017 10:52:13 -0500 Date: Fri, 15 Dec 2017 10:52:10 -0500 (EST) Message-Id: <20171215.105210.103516329605719086.davem@davemloft.net> To: pavel@ucw.cz Cc: nix.or.die@gmail.com, bpoirier@suse.com, lsorense@csclub.uwaterloo.ca, aaron.f.brown@intel.com, jeffrey.t.kirsher@intel.com, linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org Subject: Re: v4.15-rc2 on thinkpad x60: ethernet stopped working From: David Miller In-Reply-To: <20171215092849.GB15090@amd> References: <20171210083949.GA3872@amd> <20171215092849.GB15090@amd> 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]); Fri, 15 Dec 2017 07:52:12 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1026 Lines: 36 From: Pavel Machek Date: Fri, 15 Dec 2017 10:28:49 +0100 > 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 > .... >> >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 > > I don't see the patch in latest mainline. Not having ethernet > is... somehow annoying. What is going on there? Generally speaking, e1000 maintainence has been handled very poorly over the past few years, I have to say. Fixes take forever to propagate even when someone other than the maintainer provides a working and tested fix, just like this case. Jeff, please take e1000 maintainence seriously and get these critical bug fixes propagated. Thank you.