Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 200195] New: [Regression] Network does not come back after suspend
Date: Fri, 6 Jul 2018 14:23:12 -0700	[thread overview]
Message-ID: <20180706142312.75412c39@xeon-e3> (raw)



Begin forwarded message:

Date: Fri, 22 Jun 2018 18:04:00 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 200195] New: [Regression] Network does not come back after suspend


https://bugzilla.kernel.org/show_bug.cgi?id=200195

            Bug ID: 200195
           Summary: [Regression] Network does not come back after suspend
           Product: Networking
           Version: 2.5
    Kernel Version: 4.17.2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: aacid@kde.org
        Regression: No

Created attachment 276753
  --> https://bugzilla.kernel.org/attachment.cgi?id=276753&action=edit  
lspci -vvv output

Setup:
 * Using Archlinux
 * Using wired network

Only difference is using kernel 4.17.2 vs kernel 4.16.13

When using 4.17.2, the network does not work after resuming from suspend. With
4.16.13 it works as expected.

My guess is that this is driver/hardware dependent since i have another machine
with the same setup and it does not seem to have that regression.

I'm attaching the lspci output of 4.16.13.

Anything else I can provide or test to pinpoint where the regression happened
please do not hesitate to ask.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-07-06 21:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180706142312.75412c39@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox