Bug 1390747

Summary:	Unable to suspend after using external USB 3.0 drive
Product:	[Fedora] Fedora	Reporter:	Mario Curcija <mario.curcija>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	27	CC:	gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mario.curcija, mchehab
Target Milestone:	---	Flags:	jforbes: needinfo?
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:	2018-08-29 15:01:43 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:

Description Mario Curcija 2016-11-01 19:48:39 UTC

Thi is actually a clone of the Bug 1199883 which was closed due to EOL mass-update. I finally found some time to test few older bugs on 25 Beta.

Reproducible always using Fedora 25 Workstation Beta (live), as well as on F22 (see Bug 1199883), F23 and F24:

Steps to Reproduce:
1. Attach an external USB 3.0 drive
2. Mount and touch something on mounted file system and unmount afterwards. 
3. Disconnect drive
4. Try to suspend 

Actual results: System wakes up immediately. 

Expected results: System goes in suspend state (and stays suspended)

Additional info:
I was able to fix this issue using following steps:
1. attach same device again
2. suspend - system suspends as expected 
3. wake up and disconnect drive

Suspending system afterwards works as expected.

Comment 1 Mario Curcija 2016-11-02 18:37:38 UTC

Reproducible on following hardware: N56JR (ASUS-NotebookSKU). 
I was not able to reproduce described behavior on: 
* Lenovo Flex 2-15 and 
* HP 15-ba014ng

Comment 2 Laura Abbott 2017-01-17 01:13:22 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 Mario Curcija 2017-01-23 18:39:32 UTC

Still reproducible (workaround as well) on Asus N56JR on 4.9.4-201.fc25.x86_64.

Comment 4 Justin M. Forbes 2017-04-11 14:38:37 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.10.9-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 5 Mario Curcija 2017-04-16 15:49:34 UTC

Still reproducible (workaround as well) on Asus N56JR using Fedora-Workstation-Live-x86_64-26_Alpha-1.7.

Comment 6 Laura Abbott 2018-02-28 03:41:33 UTC

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  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 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 7 Mario Curcija 2018-04-16 19:42:51 UTC

Still reproducible (workaround as well) on Asus N56JR (4.15.14-300.fc27.x86_64)
Version set to F27

Comment 8 Justin M. Forbes 2018-07-23 15:05:09 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  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 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 9 Justin M. Forbes 2018-08-29 15:01:43 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.