Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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