Bug 1374495

Summary: [REGRESSION] kernel-4.7.2-201.fc24.x86_64 KMS causes blank screen on Intel HD Graphics 5500
Product: [Fedora] Fedora Reporter: James <james>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 24CC: ajax, mikko.cal, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:12:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg from broken session
none
dmesg from working session (kernel 4.6) none

Description James 2016-09-08 20:18:32 UTC
Created attachment 1199195 [details]
dmesg from broken session

Description of problem:
Since upgrading to kernel-4.7.2-201.fc24.x86_64, as soon as KMS kicks in the screen is blank and remains so. Otherwise the machine is active. I can Ctrl+Alt+Del to go back to kernel-4.6.7-300.fc24.x86_64, which is OK.

How reproducible:
Consistently.

Additional info:
The machine is a Lenovo C50-30 with Intel HD Graphics 5500 and an nVidia 820A chip in an Optimus configuration. I've blacklisted nouveau. Never had any trouble like this with it before.

Comment 1 James 2016-09-08 20:19:00 UTC
Created attachment 1199196 [details]
dmesg from working session (kernel 4.6)

Comment 2 James 2016-09-08 20:25:42 UTC
Displays if nomodeset given on cmdline, but no fancy GL.

Comment 3 James 2016-09-14 00:22:28 UTC
I can't see anything untoward in the dmesg logs. Are there any cmdline options I can try for extra info or workaround? This is pretty bad, a deal-breaker for kernel 4.7 on this machine.

Comment 4 James 2016-09-14 00:27:39 UTC
Added what looks like the same thing reported on FDO bugzilla. Funny how this only happens on one of my machines, the others (with different i915 chips) are all OK.

Bug 1373031 might be the same thing, too.

Comment 5 James 2016-09-14 21:23:26 UTC
There's an upstream fix for this:

https://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=ea54ff4008892b46c7a3e6bc8ab8aaec9d198639

I've applied the patch to a local-build kernel-core-4.7.3-200.jhe.fc24.x86_64 and things are back as they should be.

Comment 6 James 2016-09-23 20:39:27 UTC
Still broken in kernel-4.7.4-200.fc24.x86_64. Please get this patch back into the Fedora set.

Comment 7 James 2016-10-01 09:37:28 UTC
Fixed in kernel-4.7.5-200.fc24.x86_64.

Comment 8 Fedora End Of Life 2017-07-25 22:55:18 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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.

Comment 9 Fedora End Of Life 2017-08-08 17:12:14 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.