From: Greg KH <greg@kroah.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: "rwarsow@gmx.de" <rwarsow@gmx.de>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Regression in e1000e since Kernel 4.14.3
Date: Tue, 5 Dec 2017 10:23:20 +0100 [thread overview]
Message-ID: <20171205092320.GA766@kroah.com> (raw)
In-Reply-To: <24f11edf-4fb7-3067-78da-27221b562ba4@gmail.com>
On Tue, Dec 05, 2017 at 10:16:03AM +0100, Gabriel C wrote:
> On 05.12.2017 09:53, Greg KH wrote:
> > 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? :)
> >
>
> Greg,
>
> last time I reported something about e100* someone told me to just CC netdev =)
>
> However the issue still remains with 4.14.4-rc1 and NM , and is still fine with connman.
>
> I don't even think is something about the driver itself because I've quick compiled the out-of-tree-e1000e
> and breaks with NM in the same way. ( which should not be possible ? )
>
> Even when 4.14.3 was biggiSH :) after a quick scan and assuming the e1000e patches are fine , remaining candidates
> should be the IRQ* and x86/* ones ?
I am not assuming the e1000e patches are all fine :)
Any chance you can do a 'git bisect' between 4.14.2 and 4.14.3 to find
the offending patch?
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-05 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:10 Regression in e1000e since Kernel 4.14.3 rwarsow
2017-12-04 23:47 ` Gabriel C
2017-12-05 6:18 ` Greg KH
2017-12-05 6:19 ` Greg KH
2017-12-05 8:20 ` Gabriel C
2017-12-05 8:53 ` Greg KH
2017-12-05 9:16 ` Gabriel C
2017-12-05 9:23 ` Greg KH [this message]
2017-12-05 9:55 ` Gabriel C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171205092320.GA766@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=rwarsow@gmx.de \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.