Created attachment 1044946 [details] chromium artefacts Description of problem: I had perfectly running Fedora 21 desktop for over a year and few weeks ago strange things started happening. I was running pure Desktop with Gnome 3 but wanted to try out Cinnamon and Mate desktops also. After installing those desktops (but could be also due to intel driver update at the same time) I got unusable destop afterwards. Chromium blinks and has artefact issues (attached) after few minutes of using it. It works fine for first few minutes. Also scrolling in Chromium blinks whole display. External 4K monitor worked fine on 3840x2160 resolution, but now it only works up to 2560x1600 resolution. I'm using Lenovo T440s with Intel i7-4600U CPU and Haswell graphics. I also notices that /proc/self/exe is using 90% of one CPU core. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1044948 [details] chromium causing screen to blink on scroll
Here is full line from /proc/self/exe that is using 90% of CPU: valent 2839 82.1 16.0 9892984 1952976 ? Rl 10:10 15:20 /proc/self/exe --type=gpu-process --channel=2811.0.1936921852 --supports-dual-gpus=false --gpu-driver-bug-workarounds=2,15,44 --disable-accelerated-video-decode --gpu-vendor-id=0x8086 --gpu-device-id=0x0a16 --gpu-driver-vendor --gpu-driver-version Does this mean that my GPU is running in non-accelerated mode?
When closing Chromium I also see /proc/self/exe process gets closed. I can use Firefox instead of Chromium so this is not crucial issue for me. My main concer is still not being able to use 4K monitor on full resolution, I got used to it and it is crucial for my productive work. What kind of logs would show what is the issue with intel driver now being able to run external monitor on 3840x2160 resolution ? Is this a know issue with some X.org or Intel driver update? Can I revert back to some older but more stable driver?
I tried solution suggested by Fedora Magazine [1] and installed new kernel from updates-testing on my F21 and rebooted. It is still same issue; I can't even enable external 4K display. When I plug it in both screens blink on/off for few times and then 4K display just goes to off for few seconds, and cycle repeats. I reverted back to older kernels, and some time I can enable lover resolution but sometimes I can't because Xorg reverts back to high resolution and fails. I also tried running Gnome on Wayland. Plugging in external monitor has absolutely no effect. Like hotplug is completely disabled under Wayland or probably not working. Any ideas or tips? Which logs can I send that would help to troubleshoot this issue? [1] http://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/
This is xrand setup that currently works: xrandr --output VIRTUAL1 --off --output eDP1 --mode 1920x1080 --pos 0x1600 --rotate normal --output DP1 --mode 2560x1600 --pos 0x0 --rotate normal --output HDMI2 --off --output HDMI1 --off --output DP2 --off
Created attachment 1045244 [details] plugging in external monitor
Which additional info can I share to help troubleshoot this issue further?
Forcing Asus 4k monitor to 30Hz now 4k resolution works. It looks like somehow driver can't read data from monitor and tries to work on 60Hz and that fails.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.