Bug 1019765

Summary: After suspend usb network interface is unavailable
Product: [Fedora] Fedora Reporter: Artur Szymczak <ajes+redhat>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw, johannbg, lnykryn, mschmidt, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:39:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg
none
lsusb none

Description Artur Szymczak 2013-10-16 11:15:01 UTC 
Created attachment 812868 [details]
dmesg

Description of problem:
systemctl suspend suspends my system, but after wakeing up, usb ethernet adapter is turned off. I have to remove it and plug it again to start working.
USB device is listed in lsusb (before and after) suspend (attachment).

Version-Release number of selected component (if applicable):
systemd-208-2.fc20.x86_64
NetworkManager-0.9.9.0-14.git20131003.fc20.x86_64
kernel-3.11.4-302.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1. https://fedoraproject.org/wiki/QA:Testcase_Power_Management_Suspend
2.
3.

Actual results:
USB doesn't work

Expected results:
Should be available.

Additional info:
Comment 1 Artur Szymczak 2013-10-16 11:16:46 UTC 
Created attachment 812870 [details]
lsusb
Comment 2 Michal Schmidt 2013-10-19 09:24:35 UTC 
systemd is not directly involved in configuring network interfaces.
I don't know if NetworkManager does (or should do) anything to USB ethernet adapters on suspend/resume or if it's purely a kernel problem. Reassigning tentatively to NM.
Comment 3 Fedora End Of Life 2015-05-29 09:34:57 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2015-06-29 12:39:02 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.