Bug 787213

Summary: System crash Intel Corporation 82Q963/Q965
Product: Red Hat Enterprise Linux 6 Reporter: Nickolay Bunev <just4nick>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2CC: tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 12:00:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 842499    
Attachments:
Description Flags
/var/log/messages
none
Xorg.0.log.with.nomodeset
none
Xorg.0.log.with.drm.04.without.nomodeset
none
dmesg.with.modeset
none
dmesg.without.nomodeset none

Description Nickolay Bunev 2012-02-03 15:09:49 UTC 
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.
Comment 1 Nickolay Bunev 2012-02-03 15:10:49 UTC 
Created attachment 559304 [details]
Xorg.0.log.with.nomodeset
Comment 2 Nickolay Bunev 2012-02-03 15:11:33 UTC 
Created attachment 559305 [details]
Xorg.0.log.with.drm.04.without.nomodeset
Comment 3 Nickolay Bunev 2012-02-03 15:12:05 UTC 
Created attachment 559306 [details]
dmesg.with.modeset
Comment 4 Nickolay Bunev 2012-02-03 15:12:59 UTC 
Created attachment 559307 [details]
dmesg.without.nomodeset
Comment 7 Suzanne Logcher 2012-02-14 23:30:39 UTC 
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.
Comment 8 Jan Kurik 2017-12-06 12:00:49 UTC 
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/