Bug 602080

Summary: X server causes unnecessary fb resize on startup
Product: Red Hat Enterprise Linux 6 Reporter: Ben Skeggs <bskeggs>
Component: xorg-x11-serverAssignee: Ben Skeggs <bskeggs>
Status: CLOSED CURRENTRELEASE QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: mgordon, syeghiay, vbenes
Target Milestone: rcKeywords: Patch, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xorg-x11-server-1.7.7-6.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-15 14:52:23 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
patch correcting the issue none

Description Ben Skeggs 2010-06-09 05:35:44 UTC
Created attachment 422441 [details]
patch correcting the issue

In multiple display configurations, due to a typo in the X server, the initial framebuffer will be sized to only fit a single display, resulting in a resize at a later point during init.

This unnecessary resize causes memory fragmentation, which can be a big problem on cards with a limited amount of video memory.

Comment 1 RHEL Program Management 2010-06-09 05:54:14 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 3 Ben Skeggs 2010-06-09 23:42:40 UTC
MODIFIED xorg-x11-server-1.7.7-6.el6 is in brew.

Comment 5 Vladimir Benes 2010-11-12 13:40:26 UTC
randr-initial patch looks sana is present in newest package and is applied in spec file 
-> SanityOnly

Comment 6 releng-rhel@redhat.com 2010-11-15 14:52:23 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.