public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Pavel Machek <pavel@ucw.cz>, jacob.e.keller@intel.com
Cc: bpoirier@suse.com, nix.or.die@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	lsorense@csclub.uwaterloo.ca, David Miller <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] v4.15-rc2 on thinkpad x60: ethernet stopped working
Date: Wed, 20 Dec 2017 08:24:04 +0200	[thread overview]
Message-ID: <842e2aec-77c6-277c-aeef-b506296f6599@intel.com> (raw)
In-Reply-To: <077087f2-551a-c045-6b07-b1b661e53dad@intel.com>

On 12/18/2017 17:50, Neftin, Sasha wrote:
> On 12/18/2017 13:58, Pavel Machek wrote:
>> On Mon 2017-12-18 13:24:40, Neftin, Sasha wrote:
>>> On 12/18/2017 12:26, Pavel Machek wrote:
>>>> 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.
>>>> No response AFAICT. I guess I should test reverting
>>>> 19110cfbb34d4af0cdfe14cd243f3b09dc95b013, then ask you for revert?
>>> Hello Pavel,
>>>
>>> Before ask for reverting 19110cfbb..., please, check if follow patch of
>>> Benjamin work for you http://patchwork.ozlabs.org/patch/846825/
>> Jacob said, in another email:
>>
>> # 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.
>>
>> ...which makes me think that revert is preffered?
>>
>>                                     Pavel
>>
> Pavel, before ask for revert - let's check Benjamin's patch following 
> to his previous patch. Previous patch was not competed and latest one 
> come to complete changes.
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

Pavel, any update? Is Benjamin's last patch solved your network problem?

  parent reply	other threads:[~2017-12-20  6:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10  8:39 v4.15-rc2 on thinkpad x60: ethernet stopped working Pavel Machek
2017-12-10 12:44 ` Gabriel C
2017-12-15  9:28   ` Pavel Machek
2017-12-15 15:52     ` David Miller
2017-12-18 10:26       ` Pavel Machek
     [not found]         ` <5c0be4c4-5a56-cc7b-7b5a-345f446e788e@intel.com>
2017-12-18 11:58           ` [Intel-wired-lan] " Pavel Machek
2017-12-18 15:50             ` Neftin, Sasha
2017-12-18 17:07               ` Fujinaka, Todd
2017-12-20 15:54                 ` Pavel Machek
2017-12-20 16:01                   ` Pavel Machek
2017-12-21  7:13                     ` Neftin, Sasha
2017-12-20  6:24               ` Neftin, Sasha [this message]
2017-12-15 17:29   ` Keller, Jacob E
2017-12-15 17:30     ` Keller, Jacob E
2017-12-15 19:04       ` Pavel Machek
2017-12-21  9:40 ` [Intel-wired-lan] " Paul Menzel

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=842e2aec-77c6-277c-aeef-b506296f6599@intel.com \
    --to=sasha.neftin@intel.com \
    --cc=bpoirier@suse.com \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@vger.kernel.org \
    --cc=nix.or.die@gmail.com \
    --cc=pavel@ucw.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox