Bug 602080 - X server causes unnecessary fb resize on startup
X server causes unnecessary fb resize on startup
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Ben Skeggs
: Patch, Triaged
Depends On:
  Show dependency treegraph
Reported: 2010-06-09 01:35 EDT by Ben Skeggs
Modified: 2010-11-15 09:52 EST (History)
3 users (show)

See Also:
Fixed In Version: xorg-x11-server-1.7.7-6.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-15 09:52:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch correcting the issue (1.43 KB, patch)
2010-06-09 01:35 EDT, Ben Skeggs
no flags Details | Diff

  None (edit)
Description Ben Skeggs 2010-06-09 01:35:44 EDT
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 Product and Program Management 2010-06-09 01:54:14 EDT
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
Comment 3 Ben Skeggs 2010-06-09 19:42:40 EDT
MODIFIED xorg-x11-server-1.7.7-6.el6 is in brew.
Comment 5 Vladimir Benes 2010-11-12 08:40:26 EST
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 09:52:23 EST
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.

Note You need to log in before you can comment on or make changes to this bug.