Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Janssen <medhefgo@web.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Regression: e1000e link not coming up
Date: Sat, 16 Nov 2019 12:50:38 +0100	[thread overview]
Message-ID: <3945198.J3aOToa6sv@minako> (raw)

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.

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'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



             reply	other threads:[~2019-11-16 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16 11:50 Jan Janssen [this message]
2019-11-18 18:29 ` [Intel-wired-lan] Regression: e1000e link not coming up Jeff Kirsher
2019-11-19  6:12   ` Neftin, Sasha
2019-11-20  8:34     ` Neftin, Sasha
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=3945198.J3aOToa6sv@minako \
    --to=medhefgo@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox