From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Regression: e1000e link not coming up
Date: Wed, 20 Nov 2019 10:34:31 +0200 [thread overview]
Message-ID: <e68c0b03-e05b-735d-1bce-8f12aaa073aa@intel.com> (raw)
In-Reply-To: <96bdb43e-2a7b-028c-c9ed-98e4477f6b7d@intel.com>
On 11/19/2019 08:12, Neftin, Sasha wrote:
> On 11/18/2019 20:29, Jeff Kirsher wrote:
>> On Sat, 2019-11-16 at 12:50 +0100, Jan Janssen wrote:
>>> Hi,
>>>
>>> since 5.3 my I219-V network interface sometimes doesn't come up when
>>> booting
>>> or resuming from suspend. This either forces me to use "ip link
>>> down/up" or
>>> reloading the module to get working internet.
>>>
>>> I reported this issue previously to netdev at vger.kernel.org where I
>>> initially
>>> bisected to a wrong commit. After finding the right one nobody
>>> reacted to it,
>>> so now I am trying this again here.
>>
>> I apologize, this is the correct mailing list for issues with the Intel
>> wired LAN.
>>
>>
>>> There is also a bugzilla entry for this, but it seems to be ignored
>>> by
>>> maintainers too: https://bugzilla.kernel.org/show_bug.cgi?id=205067
>>> For me, this happens with systemd-networkd, but the people in the
>>> bugzilla
>>> report are observing this with NetworkManager.
>>>
>>> The commit introducing the bug is
>>> 59653e6497d16f7ac1d9db088f3959f57ee8c3db
>>> (e1000e: Make watchdog use delayed work) and reverting it did make
>>> this bug go
>>> away. Though, it cannot be reverted automatically on the latest git
>>> tree from
>>> Torvalds anymore.
>>
>> I will work with the e1000e driver lead (Sasha Neftin) to work up a
>> patch that will apply to David Miller's net tree.? I will make sure you
>> are CC'd on the patch, so you will know when it makes it into the
>> upstream kernel.
>>
> I heard a lot of peoples complain about a problem with using
> delayed_work struct in e1000e. I would suggest reverting this patch.
Looks reverting of this patch solved also the
https://bugzilla.kernel.org/show_bug.cgi?id=205047
>>> I've also tried the master branch on jkirsher/net-queue.git? and
>>> jkirsher/next-queue.git, but the bug is still present there too.
>>>
>>> This bug is really annoying and inconvenient, so I would really
>>> appreciate if
>>> somebody could fix this bug or at least have the offending commit
>>> reverted.
>>>
>>> Regards,
>>> Jan
>>>
>>>
>>
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2019-11-20 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 11:50 [Intel-wired-lan] Regression: e1000e link not coming up Jan Janssen
2019-11-18 18:29 ` Jeff Kirsher
2019-11-19 6:12 ` Neftin, Sasha
2019-11-20 8:34 ` Neftin, Sasha [this message]
2019-12-12 13:07 ` Jan Janssen
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=e68c0b03-e05b-735d-1bce-8f12aaa073aa@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.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.