From: Jan Janssen <medhefgo@web.de>
To: netdev@vger.kernel.org
Cc: Vedang Patel <vedang.patel@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Regression: Network link not coming up after suspend/resume cycle
Date: Sun, 29 Sep 2019 21:20:34 +0200 [thread overview]
Message-ID: <71354431.m7NQiGp1Tu@minako> (raw)
Hi,
I've been noticing lately that my network link sometimes does not go up
after a suspend resume cycle (roughly 1 or 2 out of 10 times). This also
sometimes happens with a fresh boot too. Doing a manual
"ip link set down/up" cycle resolves this issue.
I was able to bisect it to the commit below (or hope so) and also CCed
the maintainer for my driver too.
This is happening on a up-to-date Arch Linux system with a Intel I219-V.
Jan
7ede7b03484bbb035aa5be98c45a40cfabdc0738 is the first bad commit
commit 7ede7b03484bbb035aa5be98c45a40cfabdc0738
Author: Vedang Patel <vedang.patel@intel.com>
Date: Tue Jun 25 15:07:18 2019 -0700
taprio: make clock reference conversions easier
Later in this series we will need to transform from
CLOCK_MONOTONIC (used in TCP) to the clock reference used in TAPRIO.
Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Signed-off-by: Vedang Patel <vedang.patel@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sched/sch_taprio.c | 30 ++++++++++++++++++++++--------
1 file changed, 22 insertions(+), 8 deletions(-)
next reply other threads:[~2019-09-29 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 19:20 Jan Janssen [this message]
2019-09-29 23:26 ` Regression: Network link not coming up after suspend/resume cycle Vladimir Oltean
2019-09-30 18:34 ` 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=71354431.m7NQiGp1Tu@minako \
--to=medhefgo@web.de \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vedang.patel@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).