Bug 1674584

Summary: Deadlock after resume
Product: Red Hat Enterprise Linux 8 Reporter: Jiri Koten <jkoten>
Component: mutterAssignee: Jonas Ådahl <jadahl>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: fmuellner, ofourdan, rstrode, tpelka
Target Milestone: rcKeywords: Regression
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-12 13:08:20 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1635157    
Attachments:
Description Flags
gnome-shell backtrace
none
journal none

Description Jiri Koten 2019-02-11 16:28:30 UTC
Created attachment 1529134 [details]
gnome-shell backtrace

Description of problem:
After resume (mostly the second time) I end up with blank screen and cannot switch to VT. Remote login to the machine shows gnome-shell process (user session and gdm session) are eating 100% CPU. 

From the backtrace it looks like deadlock.  

Both gdm and user sessions are Wayland. The attached backtrace is from machine with NVidia GPU using the binary driver but I was able to reproduce this also on my laptop with intel gpu.

It's a regression as this didn't happened before in rhel8 I suspect it happened after mutter-3.28.3-11.el8, but I have to retest to be sure.


Version-Release number of selected component (if applicable):
gnome-shell-3.28.3-9.el8
mutter-3.28.3-16.el8

How reproducible:
100%

Steps to Reproduce:
1. Login to gnome session
2. Suspend/Resume
3. Suspend/Resume

Actual results:
deadlock

Expected results:
The resume is successful 

Additional info:

Comment 2 Jiri Koten 2019-02-11 16:30:05 UTC
Created attachment 1529136 [details]
journal

Comment 3 Jonas Ådahl 2019-02-12 07:48:03 UTC
Ray pushed a potential fix to https://bugzilla.redhat.com/show_bug.cgi?id=1663440 that should solve this. If it does, we can close this as a duplicate.

Comment 4 Jiri Koten 2019-02-12 13:08:20 UTC

*** This bug has been marked as a duplicate of bug 1663440 ***