8086:1616 Display goes black at random times

Status changed to 'Confirmed' because the bug affects multiple users.

Here the section of the syslog of one of these events.

Adam Carter, thank you for reporting this and helping make Ubuntu better. To see if this is already resolved in Ubuntu, could you please test for this via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

I ran into the same issue on fresh install of Willy after rebooting from installing the latest updates

Linux regulus 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Adam Carter, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

I have gone ahead and installed the latest rc

Linux regulus 4.3.0-040300rc5-generic #201510111530 SMP Sun Oct 11 19:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

The issue is still there. Please let me know if there is any additional information I can provide, or any other way I can help this along.

Thanks for your time on this!

It could be entirely coincidental but it seems to be happening way more frequently with 4.3 then with 3.19. I've had it blank 6 times since I've upgraded kernels less then an hour ago.

Adam Carter, could you please test for this with the latest Intel kernel (drm-intel-nightly) and advise to the results?

If reproducible, please post your dmesg with the above kernel, and after booting with drm.debug=14 kernel boot parameter.

I've been testing it heavily today and its looking like the problem is fixed on drm-intel 4.3.0-994 I'm still getting the "i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment" messages but no screen blank outs so far (not sure if the message is relevant any ways).

I'm going to give it a couple days of testing before I'm convinced its fixed, but for now it's looking like the problem is resolved.

If I can ask one question what is the drm-intel branch? I'm assuming this is the development branch of the kernel is this correct? If you could can you provide me a link so I can read up on it. I'd love to understand it better.

I haven't been able to reproduce it on 4.3.0-994-generic. The problem seems to be solved running this kernel.

Adam,

thanks for your testing with this. How do we get the fix back ported to 4.2 branch? is that even possible??

Sadly that is outside of my know how. I'm hoping that some one involved with Sputnik or someone else will be able to make sense of this and provide a fix.

I have had the screen flash a few times since updating kernels but haven't looked into that yet. Besides that everything seems to work as it should.

Adam Carter, to see if the fixes in intel-drm-nightly landed in mainline already, could you please test the latest mainline kernel (4.3-rc6) and advise to the results?

Its still happening on 4.3-rc6

Adam Carter, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (intel-gfx)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

Thanks, I'll go ahead and do that but I'm having trouble finding the link (or email?) of where to report this bug in https://wiki.ubuntu.com/Bugs/Upstream/kernel only information on how to formate it.

I am also unsure of where to send it, my guess is
http://lists.freedesktop.org/mailman/listinfo/intel-gfx is this correct?
I was assuming it would be on kernel.org.

I tried to find examples of bugs on that list but couldn't any ones in
the asked for format.

I'm pretty confused about how to file the upstream report. If you'd
have the time to clear this up or point in the right direction I'd
really appreciate it.

I haven't done this before I rather take the time to get it right to begin with.

Adam Carter, I made a slight error in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507073/comments/16 . You actually want to send it to the maintainers Daniel Vetter and Jani Nikula, and CC intel-gfx.

Same issue being discussed here: http://ubuntuforums.org/showthread.php?t=2301071&page=6&p=13393733#post13393733 (with links to potential solutions ) Kernel 4.3 still has the issue for me on a new (late 2015) XPS 15 running Nvidia's 355 driver.

Having this same issue on 4.4

Dell XPS 13 9350 (2016)
Non-touch 13.3” FHD AG (1920 x 1080) InfinityEdge display
Intel® Skylake ULT GT2

Ubuntu 15.10
Kernel: 4.4.1-040401-generic #201601311534 SMP Sun Jan 31 20:36:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux