Created attachment 322160 [details] Xorg.0.log Description of problem: The performance of the glxgears benchmark is not up to expected levels. It draws per second only one third of the frames drawn by glxgears on earlier Fedora versions. Version-Release number of selected component (if applicable): glx-utils-7.2-0.13.fc10.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install Fedora rawhide as of 2008-10-31 2. Run glxbenchmark Actual results: 1221 frames in 5.0 seconds = 244.128 FPS Expected results: I do not remember the value exactly but I believe it was about 750fps on F9. I get 902fps on a very similar hardware (same graphics chip, different CPU). Additional info: A. I am aware glxgears is a very selective benchmark but it is the simplest diagnostics tool available. B. The intel driver produces some random noise in Xorg.0.log
Created attachment 322161 [details] dmesg dmesg contains a following report: [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pi pe 0
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
1. I have no /etc/X11/xorg.conf file - I run in the full autodetection mode. 2. Xorg.0.log is attached already!
(In reply to comment #3) > 2. Xorg.0.log is attached already! Sorry, I guess it means I have seen to many bugs today. :(
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
xorg-x11-server-Xorg-1.5.3-5.fc10.x86_64/xorg-x11-drv-i810-2.5.0-4.fc10.x86_64 give 1087-1100fps. Please consider the problem fixed - thank you!
The error is still there: [drm:i915_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 It is probably related to supsend action.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.