Bug 93711

Summary:

[bdw edp] i915 screen flickering after new start

Product:

DRI

Reporter:

flux242 <flux242>

Component:

DRM/Intel

Assignee:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Status:

CLOSED FIXED

QA Contact:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Severity:

normal

Priority:

high

CC:

intel-gfx-bugs

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

BDW

i915 features:

display/eDP

Attachments:

Description	Flags
output of the lspci -vvv	none
output of 'sudo get-edid \| edid-decode'	none
dmesg with 'drm.debug=14' kernel parameter	none

Description flux242 2016-01-14 12:31:00 UTC

Created attachment 121027 [details]
output of the lspci -vvv

to differentiate from the bug #91393 I'm creating a new one. It because I have different symptoms and end solutions offered there do not help.

Here is a video to demonstrate the problem https://www.youtube.com/watch?v=DZIR4qnfOH8

With the stock ubuntu 15.10 kernel version 4.2 this problem persists and there's no way to get rid of it. With the current drm-intel-nightly kernel:
$ uname -a
Linux chrome 4.4.0-994-generic #201601112101 SMP Tue Jan 12 02:02:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
the problem occurs only after a new boot. Then I need (almost blindly) login into my system and start 'xset dpms force off' command once or several times and then the flickering is gone even after I resume from the sleep.

$ sudo lshw -c video
  *-display               
       description: VGA compatible controller
       product: Broadwell-U Integrated Graphics
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 08
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:43 memory:e0000000-e0ffffff memory:d0000000-dfffffff ioport:1800(size=64)

Comment 1 flux242 2016-01-14 12:32:11 UTC

Created attachment 121028 [details]
output of 'sudo get-edid | edid-decode'

Comment 2 flux242 2016-01-14 12:39:52 UTC

Created attachment 121029 [details]
dmesg with 'drm.debug=14' kernel parameter

Comment 3 Jani Nikula 2016-06-17 16:55:32 UTC

We seem to have neglected this bug completely. Apologies. Is this still an issue with latest kernels?

Comment 4 flux242 2016-06-18 08:52:02 UTC

oh, you mean that the bug could simply disappear with a newer kernel version, huh? So, what newer kernel version do you mean exactly?

Comment 5 Jani Nikula 2016-06-20 09:13:41 UTC

(In reply to flux242 from comment #4)
> oh, you mean that the bug could simply disappear with a newer kernel
> version, huh? So, what newer kernel version do you mean exactly?

No promises, but please try v4.6 or v4.7-rc4.

Comment 6 flux242 2016-12-14 11:51:28 UTC

I've tested with teh 4.9 kernel and it seems like the problem is fixed with it

Comment 7 yann 2016-12-14 12:55:56 UTC

(In reply to flux242 from comment #6)
> I've tested with teh 4.9 kernel and it seems like the problem is fixed with
> it

thanks flux242. So closing as fixed

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.