Bug 274811

Summary: restrict video mode within ES1000's capability
Product: Red Hat Enterprise Linux 5 Reporter: LisaWu <liswu>
Component: xorg-x11-drv-atiAssignee: Dave Airlie <airlied>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: ajax, jglisse, jvuong, liswu, lmiksik, mdomonko, ovasik, pvine, vsharapo, woliu, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 00:40:50 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:
Bug Depends On:    
Bug Blocks: 928722    
Attachments:
Description Flags
add pixel clock check while validate mode for digital monitors none

Description LisaWu 2007-09-03 02:41:49 UTC
Description of problem:
When connect a digital monitor which supports max 1600x1200 resolution, radeon 
driver will set 1600x1200@24bit mode for output, however, this mode is out of 
ES1000's capacity. video corruption will occur in this case.

How reproducible:
Often

Steps to Reproduce:
1. install RHEL5
2. connect a digital monitor with max 1600x1200 resolution
3. startX
  
Actual results:
video corruption will occur

Additional info:
Radeon driver has its own mode validation routine for digital monitors, this 
routine forget to check clock limations for output mode.we add clock range 
check in this routine to restrict output mode within chip's capability.

Comment 1 LisaWu 2007-09-03 02:41:49 UTC
Created attachment 184951 [details]
add pixel clock check while validate mode for digital monitors

Comment 5 Jérôme Glisse 2013-04-16 19:38:29 UTC
Patch already applied for https://bugzilla.redhat.com/show_bug.cgi?id=554414 should already solve the issue.

Comment 9 errata-xmlrpc 2013-10-01 00:40:50 UTC
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.

http://rhn.redhat.com/errata/RHBA-2013-1360.html