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.
Created attachment 559303[details]
/var/log/messages
Description of problem:
System crashes completely shortly after gdm login. In some cases you can log on, but if you try to resize some app window it crashes again. When the system crash, you have to make a hard reset.
Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.16.0-1.el6.x86_64
xorg-x11-drv-vesa-2.3.0-2.el6.x86_64
xorg-x11-server-Xorg-1.10.4-6.el6_2.1.x86_64
kernel-2.6.32-220.4.1.el6.x86_64
dracut-kernel-004-256.el6.noarch
How reproducible:
Always
Steps to Reproduce:
1. Switch on the machine
2. Try to log in
Actual results:
System crash
Expected results:
No crash
Additional info:
I have tried the following:
1. Kernel update in favor of BZ#768288 . I saw a comment in the CentOS bug about the same issue which mentions some system crashes. - no success
2. Downgrade to kernel - 2.6.32-131.12.1 - no success
3. There is some ACPI warnings in /var/log/messages - so booting with acpi=off, noapic, etc - no change
4. Initially there was not xorg.conf, so I've created one - with "Xorg -configure". I've tried to boot with vesa, but X server doesn't start at all. There was no change so I removed the xorg.conf
5. There is a bug (BZ#657664) which mentions Q965 and nomodeset, so I decide to give it a try. Booting with nomodeset in grub.conf seems to fix the problem, but according to the Xorg.0.log it is using the vesa driver.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/