Bug 596081

Summary: [945gm] *ERROR* Hangcheck timer elapsed... GPU hung
Product: Red Hat Enterprise Linux 6 Reporter: Caolan McNamara <caolanm>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: caolanm, mcepl, mgordon
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-23 21:14:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg
none
Xorg.0.log
none
lspci output none

Description Caolan McNamara 2010-05-26 09:39:35 UTC 
Description of problem:
In RHEL6 Snapshot 5. Dell Latitude D430, 

Version-Release number of selected component (if applicable):
kernel-2.6.32-28.el6.i686
xorg-x11-drv-intel-2.11.0-4.el6.i686

How reproducible:
100%

Steps to Reproduce:
1. In RHEL6 >= Snapshot 5. A Dell Latitude D430, login and run 
x11perf -copypixwin500
  
Actual results:
Display stops refreshing. GPU hangs
Comment 1 Caolan McNamara 2010-05-26 09:40:02 UTC 
Created attachment 416731 [details]
dmesg
Comment 2 Caolan McNamara 2010-05-26 09:40:24 UTC 
Created attachment 416732 [details]
Xorg.0.log
Comment 3 Caolan McNamara 2010-05-26 09:41:07 UTC 
Created attachment 416733 [details]
lspci output
Comment 5 RHEL Program Management 2010-06-07 16:06:15 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 7 Adam Jackson 2010-06-23 21:14:43 UTC 

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