Hide Forgot
Description of problem: Whenever starting an opengl application windowed, flickering and/or tearing appears. Version-Release number of selected component (if applicable): xorg-x11-drv-intel.x86_64 2.15.0-3.fc15 (previous version was fine, at least in Neverwinter nights) How reproducible: Always. Just easier to see in a big window. Steps to Reproduce: 1. Start glxgears Actual results: Flickering/tearing Expected results: No flicker/tearing Additional info: Fullscreen modes of Neverwinter and Neverball seems to work better, but windowed is affected. My video chip is Sandybridge HD 3000 (core i5)
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 499517 [details] Xorg.0.log
Created attachment 499518 [details] dmesg
It seems syslogd crashed or misbehaves, as /var/log/messages for this boot turned out empty. Restarting without the drm.debug=0x04 does still give me an empty v.l.messages. I just noticed this when I had already uploaded the other two. I will try downgrading the logging daemon Downgrading the xorg-x11-drv-intel package to version 2.14.0-6.fc15 makes the flickering disappear.
(In reply to comment #4) > It seems syslogd crashed or misbehaves, as /var/log/messages for this boot > turned out empty. Restarting without the drm.debug=0x04 does still give me an > empty v.l.messages. I just noticed this when I had already uploaded the other > two. I will try downgrading the logging daemon Please, make a new bug for the syslog issue. Thank you
I'm seeing this too, and I've filed a bug for this upstream: https://bugs.freedesktop.org/show_bug.cgi?id=37571 See that bug for the details of my system, dmesg output, etc. Note that this also goes away when you upgrade your kernel to 2.6.39, from for example here: http://koji.fedoraproject.org/koji/buildinfo?buildID=244663
Fixed in F16 and F17, for information.
Thanks. It is fixed for me to, so lets close this bug then.