Bug 639062
| Summary: | glxgears framerate is not constant on Intel 945 (8086:27a2) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> | ||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 14 | CC: | ajax, awilliam, bruce, mcepl, xgl-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2010-10-07 03:14:49 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
John Reiser
2010-09-30 18:07:37 UTC
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 451038 [details]
/var/log/Xorg.0.log
This is the Xorg log.
There is no .conf file:
/etc/X11/xorg.conf: No such file or directory
$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
205 frames in 5.0 seconds = 40.856 FPS
248 frames in 5.0 seconds = 49.597 FPS
140 frames in 5.0 seconds = 27.958 FPS
136 frames in 5.0 seconds = 27.028 FPS
110 frames in 5.0 seconds = 21.933 FPS
125 frames in 5.0 seconds = 24.880 FPS
110 frames in 5.0 seconds = 21.891 FPS
121 frames in 5.0 seconds = 24.056 FPS
120 frames in 5.0 seconds = 23.980 FPS
154 frames in 5.1 seconds = 30.471 FPS
114 frames in 5.0 seconds = 22.754 FPS
206 frames in 5.0 seconds = 41.078 FPS
221 frames in 5.0 seconds = 44.119 FPS
Created attachment 451039 [details]
output of dmesg
Created attachment 451044 [details]
/var/log/messages
As root, /var/log/messages was copied to /tmp, then "chmod a+rw" in order to get around 0600 protection on /var/log/messages.
Jerkiness of glxgears did not go away when USB2.0 webcam was unplugged. (The cam was never used, but the USB plug is the only ON/OFF switch.)
is it smoother if you keep the CPU occupied? There's a bug several reporters seem to have where GL performance is bad if the CPU is idle... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers When the CPU is busy, then the framerate of glxgears is much closer to the rate of video refresh, but I still see some stuttering and "backwards" motion with Expose events. (Two non-overlapping Gnome-terminal shell windows, glxgears graphics window overlapping both windows. Click in sequence on title bars to hide and expose the windows.) Busy: $ while true; do date; done $ glxgears ## a different Gnome terminal window Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 294 frames in 5.0 seconds = 58.706 FPS 301 frames in 5.0 seconds = 60.017 FPS 293 frames in 5.0 seconds = 58.425 FPS 301 frames in 5.0 seconds = 60.007 FPS 292 frames in 5.0 seconds = 58.228 FPS 299 frames in 5.0 seconds = 59.626 FPS 293 frames in 5.0 seconds = 58.390 FPS 301 frames in 5.0 seconds = 60.044 FPS 283 frames in 5.0 seconds = 56.569 FPS 292 frames in 5.0 seconds = 58.274 FPS 278 frames in 5.0 seconds = 55.444 FPS 289 frames in 5.0 seconds = 57.796 FPS 278 frames in 5.0 seconds = 55.376 FPS 285 frames in 5.0 seconds = 56.878 FPS 282 frames in 5.0 seconds = 56.108 FPS 297 frames in 5.0 seconds = 59.360 FPS 292 frames in 5.0 seconds = 58.224 FPS 301 frames in 5.0 seconds = 59.975 FPS 292 frames in 5.0 seconds = 58.263 FPS 300 frames in 5.0 seconds = 59.813 FPS 292 frames in 5.0 seconds = 58.222 FPS 300 frames in 5.0 seconds = 59.804 FPS ^C $ from the numbers, it sure looks like this is: https://bugzilla.redhat.com/show_bug.cgi?id=582861 It certainly does look the same as 582861 (which has been around for 5 months.) *** This bug has been marked as a duplicate of bug 582861 *** |