Red Hat Bugzilla – Bug 310331
System hang on DELL server with ES1000 video chip
Last modified: 2013-06-21 14:42:03 EDT
Description of problem:
This issue is originally found by Dell when testing "SLES10-SP1" on their
server with RN50 video chip.
When using sax2 (Suse tool to configure display) to change resolution to
1280x1024, system hangs.
The root cause is:
Radeon driver forget to prune invalid modes after xf86ValidateModes. invalid
modes are set to output and cause video chip hang.
Created attachment 209521 [details]
add xf86PruneDriverModes after xf86ValidateModes.
Looks good to me.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Greetings Red Hat Partner,
A fix for this issue should be included in the latest packages contained in
RHEL5.2-Snapshot3--available now on partners.redhat.com.
Please test and confirm that your issue is fixed.
After you (Red Hat Partner) have verified that this issue has been addressed,
please perform the following:
1) Change the *status* of this bug to VERIFIED.
2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified)
If this issue is not fixed, please add a comment describing the most recent
symptoms of the problem you are having and change the status of the bug to ASSIGNED.
If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and I will update bugzilla for you. If you
need assistance accessing ftp://partners.redhat.com, please contact your Partner
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.