netdev - Fw: [Bug 200195] New: [Regression] Network does not come back after suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20180706142312.75412c39@xeon-e3>
Date:   Fri, 6 Jul 2018 14:23:12 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 200195] New: [Regression] Network does not come back after
 suspend



Begin forwarded message:

Date: Fri, 22 Jun 2018 18:04:00 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.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@...workplumber.org
          Reporter: aacid@....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.