Bug 1728761

Summary: Keyboard and mouse are unresponsive after ~45 days of uptime
Product: Red Hat Enterprise Linux 7 Reporter: jigar <jraising>
Component: gnome-shellAssignee: Jonas Ådahl <jadahl>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.5CC: cpippin, dbasant, fmuellner, jadahl, jkoten, jwright, kyoneyam, lilhuang, mboisver, mclasen, modehnal, titus.elverfeldt, toneata, yuokada, yzheng
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: mutter-3.28.3-17.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1766649 1778211 1778212 1778254 (view as bug list) Environment:
Last Closed: 2020-03-31 19:39: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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1766649, 1778211, 1778212, 1778254    

Description jigar 2019-07-10 15:44:26 UTC 
Description of problem: 

On a customer site, there are four servers running with RHEL 7.4. All servers stopped responding on mouse or keyboard inputs after ~45 days of uptime (+/- some days, depending on the server). 

The machines were still running and reachable via SSH. Also the software (server processes) on the machines continued working as expected. Only the desktop did not receive any inputs anymore. However, opening a xterm via SSH on the Desktop worked - although the xterm could not be used, as it did not receive any input from keyboard or mouse.

Removing and re-plugging the keyboard and the mouse directly into the machine, bypassing the KVM switch, did not help.

Version-Release number of selected component (if applicable): 
gnome-shell-3.28.3-8.el7_6
mutter-3.28.3-7.el7_6

How reproducible: Frequently ( with long uptime )

Steps to Reproduce:
1. Keep the system/server up for more than 45 days
2. Check if the keyboard & mouse are responsive
3. If unresponsive, check if it is possible to ssh to the system and work with other software

Actual results: keyboard and mouse become unresponsive

Expected results: Keyboard and mouse should not become unresponsive

Additional info:
1) On some machines, it helped to end the user session and log-in again. Other machines required a reboot.

2) This does not seem to be the Issue 02102030

3) Killing gnome-shell repairs the issue and so does switching runlevels.
Comment 9 Jonas Ådahl 2019-10-29 09:37:33 UTC 
Created attachment 1630072 [details]
timetravel.py

Attaching another tool I've been using. What it does is change the date to 10 minutes before or after the next Xorg timestamp wrap.

The bug reproduces when you go from just after the wrap, to just before, as that jump is large enough to trigger the issue.

E.g. as root, run

./timetravel.py after # jump to just after a timestamp wrap so that timestamps are now relatively small
./timetravel.py before # jump to just before the next timestamp wrap so that timestamps are now relatively large

I could reliably reproduce the issue by running these two commands; it is however possible that it will trigger already after the first, depending on what the timestamp happens to be initially.
Comment 26 errata-xmlrpc 2020-03-31 19:39:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1021