Hide Forgot
Created attachment 915373 [details] Comment (This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Created attachment 529347 [details] Xorg log file
Created attachment 529348 [details] ROM of the adapter su -c 'dd if=/dev/mem of=/tmp/rom bs=64k skip=12 count=1'
Created attachment 529349 [details] /sys/kernel/debug/dri/0/i915_opregion Optregion data
Created attachment 529350 [details] /sys/kernel/debug/dri/64/i915_opregion
Created attachment 529351 [details] Output of the glxinfo command
Could we get output of the dmesg command after the issue is reproduced, please? Thank you
Created attachment 529396 [details] dmesg output during system usage dmesg after using the system for a while
Created attachment 529398 [details] /var/log/messages since the install of the system
Comment on attachment 529398 [details] /var/log/messages since the install of the system You may notice an issue with the i915 driver throwing the following warning: Oct 20 20:37:17 xxx-acer kernel: [ 2041.909573] WARNING: at drivers/gpu/drm/i915/i915_drv.c:372 gen6_gt_force_wake_put+0x29/0x51 [i915]() I made the mistake to browse for the /sys/kernel/debug/dri/64/i915_opregion file with my browser, and this was the only time this warning was thrown. Also there seems to be an unrelated issue with the iwlagn driver for the wireless nw adapter.
Created attachment 529403 [details] Screenshot of glxgears running The tearing is not visible on the screenshot, however it is visible on the screen.
Hello, I stumbled upon a workaround for the issue: The tearing in gnome-shell disappeared after I added the following to my /etc/environment file: CLUTTER_PAINT=disable-clipped-redraws:disable-culling I am not sure how much does this affect performance.
I also have tearing problem with i965. But it only happens on the monitor plugged to DVI connector. I have dual-screen config, one monitor on DVI, another on VGA connector.
Sorry for confusion, the tearing is also visible on VGA too.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.