Bug 97867

Summary:

[HSW][Regression] 4.6.7 and beyond causes screen flickering whereas 4.5.5 works fine.

Product:

DRI

Reporter:

dalavita

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:

blocker

Priority:

highest

CC:

intel-gfx-bugs

Version:

unspecified

Keywords:

regression

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

HSW

i915 features:

Attachments:

Description	Flags
4.5.5 dmesg with drm.debug=0x1e log_buf_len=1M as boot commands	none
4.7.3 dmesg with drm.debug=0x1e log_buf_len=1M as boot commands	none
Fixed 4.7.3 dmesg dump.	none

Description dalavita 2016-09-19 17:59:51 UTC

Hello. I reinstalled a fresh Fedora version 24 64 bit from their website after formatting the previous system since I had an issue where a dnf update caused heavy screen flickering on my computer.

The formatting fixed the issue but as soon as I updated through the command sudo dnf check-update; sudo dnf update -y and restarted the issue came back. A restart and a launch into the backup kernel version 4.5.5 fixed the issue again.

I will continue to try to find this issue because it is borderline unbearable.

My computer specs are as follows:

Lenovo Thinkpad Edge E540 using an Intel i915 video card and a Geforce GT 740M.

Again, this is a completely fresh install compared to nothing but a dnf update.

As far as I know this started the very first kernel update after installing Fedora 24. I think it was 4.6.7.300 or something like that.

As of today I'm still using the old 4.5.5 kernel since thats the only one not causing screen flicker.

I have installed the latest kernel (4.7.3) and tried that and to no good effect.

Comment 1 yann 2016-09-20 07:44:14 UTC

Can you attached your kernel log (ie dmesg) where issue is occurring?
Please add to your boot command line "drm.debug=0x1e log_buf_len=1M" in order to collect more data.

Comment 2 dalavita 2016-09-20 11:52:55 UTC

Created attachment 126656 [details]
4.5.5 dmesg with drm.debug=0x1e log_buf_len=1M as boot commands

Comment 3 dalavita 2016-09-20 11:53:36 UTC

Created attachment 126657 [details]
4.7.3 dmesg with drm.debug=0x1e log_buf_len=1M as boot commands

Comment 4 dalavita 2016-09-20 11:54:15 UTC

I've added two txts with dmesg > x.txt after running the boot commands you provided.

Comment 5 yann 2016-09-20 12:07:57 UTC

(In reply to dalavita from comment #4)
> I've added two txts with dmesg > x.txt after running the boot commands you
> provided.

Thanks Dalavita, unfortunately on both case your boot command line miss drm.debug and log_buf_len parameter:

Command line: BOOT_IMAGE=/vmlinuz-4.7.3-200.fc24.x86_64 root=/dev/mapper/fedora_brute-root ro rd.lvm.lv=fedora_brute/root rd.lvm.lv=fedora_brute/swap rhgb quiet LANG=en_US.UTF-8

Comment 6 dalavita 2016-09-20 13:42:13 UTC

Created attachment 126660 [details]
Fixed 4.7.3 dmesg dump.

Comment 7 dalavita 2016-09-20 13:42:50 UTC

I have readded a fixed 4.7.3 dmesg now. Do you want one for 4.5.5 too?

Comment 8 Jari Tahvanainen 2016-12-19 10:58:21 UTC

Highest+Blocker as being regression w/o workaround.

Comment 9 dalavita 2017-01-24 10:23:50 UTC

Hello. I wanted to make a comment today saying that since 4.9.x my graphics have been normal and the screen flickering seems to have resolved itself.

To summarize. <4.5.5 and 4.9.x> seems to be working, nothing inbetween seem to be. I'm just happy I can use an up to date kernel again. Yay!

Wish I knew what bugged out to begin with.

Comment 10 yann 2017-01-24 10:28:41 UTC

(In reply to dalavita from comment #9)
> Hello. I wanted to make a comment today saying that since 4.9.x my graphics
> have been normal and the screen flickering seems to have resolved itself.
> 
> To summarize. <4.5.5 and 4.9.x> seems to be working, nothing inbetween seem
> to be. I'm just happy I can use an up to date kernel again. Yay!
> 
> Wish I knew what bugged out to begin with.

Thanks dalavita for your feedback and confirming this is fixed now. I ma closing the bug now. Please reopen in case it is occurring again.

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.