Created attachment 118486 [details] dmesg PROBLEM: - Random X.org crashes on SNA (UXA not affected - unable to reproduce) - Random system reboots (remember to happen while running 3D game) on SNA. - Artifacts in few applications (for example „phosphor” from xscreensaver) on SNA EVIDENCE: - Xorg.0.log with X.org crash (after monitor plug-out - never happen on UXA) - Random kernel WARNINGS in dmesg CONFIG: - Linux voyager 4.1.6-hardened-voyager #9 SMP Tue Sep 22 17:19:54 CEST 2015 x86_64 Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz GenuineIntel GNU/Linux - Kernel .config attached
Created attachment 118487 [details] Kernel .config
Created attachment 118488 [details] Artifacts 1
Created attachment 118489 [details] Artifacts 2
Created attachment 118490 [details] X.org log
Note: there is nothing special about xorg.conf (it does not even exist - there are only keyboard and mouse sections in xorg.conf.d/)
Step 1: do not add random dangerous module options to the kernel. Step 2: update the ddx.
1) What "random dangerous modules" do you mean? (attaching lsmod) 2) At least in Gentoo there is no newer x11-drivers/xf86-video-intel than 2.99.917-r2. Should I compile by myself bleeding edge from repo?
Created attachment 118491 [details] lsmod
"i915.enable_rc6=0 i915.enable_fbc=1 i915.lvds_downclock=1 i915.enable_execlists=0" fbc is known to be broken for that kernel, lvds downclock is meaningless for your hardware, enable_rc6=0 is a bizarre choice. They will all generate warnings and taint your kernel if you set them. Yes, grab http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ and lets see what issues actually remain.
Oh, you are right. That parameters were left after my previous hardware and enable_rc6=0 was intended to disable it (what I might misunderstood) as I know it is broken (and was used on previous hardware). I will remove those parameters and test using xf86-video-intel-9999 (from Git - Gentoo, overlay x11).
Artifacts are gone, but WARNING messages still appear to be in dmesg.
Created attachment 118500 [details] dmesg after driver upgrade and removal of dangerous kernel parameters
The warnings are mostly harmless - worse, it is a warning that something outside of our driver stack is manipulating gfx registers.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.