Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752671AbdLEIUj (ORCPT ); Tue, 5 Dec 2017 03:20:39 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:41505 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750978AbdLEIUi (ORCPT ); Tue, 5 Dec 2017 03:20:38 -0500 X-Google-Smtp-Source: AGs4zMYYqXV43/fOh4eLyDSzISJFBPUp/JioKh4QD2Maa9uMf0hSj6TYN9sGGEfU6aivjtn35HCilg== Subject: Re: Regression in e1000e since Kernel 4.14.3 To: Greg KH Cc: "rwarsow@gmx.de" , linux-kernel@vger.kernel.org, stable@vger.kernel.org, "netdev@vger.kernel.org" References: <2d4f3853-a81d-d37d-6b1c-5b4416bcb91d@gmx.de> <20171205061834.GB1341@kroah.com> <20171205061920.GC1341@kroah.com> From: Gabriel C Message-ID: <491f96ed-9394-dd2f-9af8-435159eed347@gmail.com> Date: Tue, 5 Dec 2017 09:20:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171205061920.GC1341@kroah.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 912 Lines: 28 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.