Bug 1381031

Summary: USB Ethernet device 0bda:8153 Realtek Semiconductor Corp. does not show up again after suspending
Product: [Fedora] Fedora Reporter: Volker Sobek <reklov>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, reklov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-24 16:10:48 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
journalctl -f sequence of plugging in the device, suspending and waking up
none
lsusb -v -s 002:005 of the device none

Description Volker Sobek 2016-10-02 15:13:06 UTC
Created attachment 1206623 [details]
journalctl -f sequence of plugging in the device, suspending and waking up

Description of problem:

This is an USB-to-Ethernet device, which is correctly recognized by the kernel when I plug it in while the laptop is running, but after wake from suspend, the device is now longer visible.


Version-Release number of selected component (if applicable):
4.8.0-0.rc8.git0.1.fc25.x86_64


How reproducible:
I think so far it always failed to be detected after wake from suspend.

Steps to Reproduce:
1. Boot fedora 25, plug in the USB-Ethernet device and check in journalctl -f that it is recognized by the kernel and functioning correctly 
2. Suspend the system
3. Wake up the system

Actual results:
After wake up the device is no longer visible (lsusb and journalctl) and NetworkManager can't reconnect to the network


Expected results:
The device is still there after wakeup from suspend and functioning correctly


Additional info:

Comment 1 Volker Sobek 2016-10-02 15:14:06 UTC
Created attachment 1206624 [details]
lsusb -v -s 002:005 of the device

Comment 2 Laura Abbott 2017-01-17 01:12:00 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Volker Sobek 2017-01-21 12:07:13 UTC
Fixed in 4.9.3-200.fc25. The device is now correctly detected after wakeup from suspend.

Comment 4 Laura Abbott 2017-01-24 16:10:48 UTC
Thanks for letting us know. I'm going to close the bug. Please reopen if the problem shows up again.