Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752831AbdLEJDB (ORCPT ); Tue, 5 Dec 2017 04:03:01 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:44595 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752644AbdLEJCy (ORCPT ); Tue, 5 Dec 2017 04:02:54 -0500 X-Greylist: delayed 569 seconds by postgrey-1.27 at vger.kernel.org; Tue, 05 Dec 2017 04:02:53 EST X-ME-Sender: Date: Tue, 5 Dec 2017 09:53:30 +0100 From: Greg KH To: Gabriel C Cc: "rwarsow@gmx.de" , linux-kernel@vger.kernel.org, stable@vger.kernel.org, "netdev@vger.kernel.org" Subject: Re: Regression in e1000e since Kernel 4.14.3 Message-ID: <20171205085330.GC16055@kroah.com> References: <2d4f3853-a81d-d37d-6b1c-5b4416bcb91d@gmx.de> <20171205061834.GB1341@kroah.com> <20171205061920.GC1341@kroah.com> <491f96ed-9394-dd2f-9af8-435159eed347@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <491f96ed-9394-dd2f-9af8-435159eed347@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1160 Lines: 30 On Tue, Dec 05, 2017 at 09:20:33AM +0100, Gabriel C wrote: > On 05.12.2017 07:19, Greg KH wrote: > > On Tue, Dec 05, 2017 at 07:18:34AM +0100, Greg KH wrote: > > > On Tue, Dec 05, 2017 at 12:47:10AM +0100, Gabriel C wrote: > > > > On 04.12.2017 23:10, rwarsow@gmx.de wrote: > > > > > > > > > Hallo > > > > > > > > > > someone and I got an regression with e1000e since kernel 4.14.3 and it seems there is 4.14.4 on the way without a fix. > > > > > > > > > > > > > > > bug report is here: > > > > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=198047 > > > > > > > > ( added stable and netdev to CC ) > > > > > > > > Yes I have a box with e1000e and it seems something at least breaks NM after 4.14.3. > > > > > > Again, can people try 4.14.5-rc1? It should be resolved there. > > > > Oops, that would be 4.14.4-rc1. Any why do you say above that is on the > > way without a fix, did you test it? > > I didn't tested 4.14.4-rc1 but somone from the bug report tested it and told is not resolved. > > I'll fire up an build in a bit and let you know. Great, and maybe cc: the developers and mailing list for this driver at the same time? :)