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.

Created attachment 435261 [details]
Xorg log

Patched my i865 machine this morning and when it booted, X was completely unresponsive. The mouse cursor wouldn't move, and it didn't respond to any keyboard presses (not even ctrl-alt-f*).

I could ssh into the machine however. There were no backtraces or anything in the ring buffer, and the Xorg log didn't seem to show anything as being wrong. I could also make it switch between runlevel 3 and 5, and that worked, but X was always unresponsive when it was up. It was just running gdm at the time.

Booting to -52.el6 got it working again, so it seems like a regression that crept in in -53 or -54.

Attaching Xorg log and dmesg from when the machine was in this state, but nothing in them jumped out at me as pointing to the problem.

Created attachment 435262 [details]
dmesg

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