Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 883667

Summary: X freezes with "[drm:drm_mode_getfb] *ERROR* invalid framebuffer id" error
Product: Red Hat Enterprise Linux 6 Reporter: mjin <mjin>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: cww, mjin, tlavigne, tpelka, wili
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-15 18:40:37 UTC Type: Bug
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: 1075802, 1159931    
Attachments:
Description Flags
Xorg file none

Comment 1 mjin 2012-12-05 05:48:04 UTC
Description of problem:

X freezes after system flip into slip into power(sleep) save mode.

Dec  3 16:40:22 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Dec  3 16:42:46 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
Dec  3 16:42:55 localhost kernel: [drm:drm_mode_getfb] *ERROR* invalid framebuffer id


Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux Server release 6.1 (Santiago)
2.6.32-131.0.15.el6.x86_64

How reproducible:


Steps to Reproduce:
1.boot system
2.after a while, system slip into power save mode
3.X can never be awaken after that,
  
Actual results:


Expected results:


Additional info:

Only X freezes, console works fine(ctrl+atl+f4)

Comment 2 mjin 2012-12-05 05:49:34 UTC
Created attachment 657988 [details]
Xorg file

Comment 4 RHEL Program Management 2012-12-14 07:17:14 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2013-10-14 04:34:12 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 15 Jérôme Glisse 2015-02-27 20:43:09 UTC
So i can't remember why i acked those but i can't reproduce using 6.1 so i am not sure this is fix or not.

Comment 16 Jérôme Glisse 2015-03-23 21:31:08 UTC
The original error message is no longer present with RHEL > 6.2, thus we believe this bug is fix. If you are still experiencing this issue with newer RHEL, please report, otherwise we will close this bug.

Comment 17 Chris Williams 2015-05-15 18:40:37 UTC
Closing this BZ based on Comment 16.
If the issue is not resolved in the 6.7 beta, please re-open this BZ.