Bug 1251994 - WARNING: CPU: 0 PID: 970 at drivers/gpu/drm/i915/intel_display.c:5615 intel_modeset_check_state+0xaec/0xc60 [i915]()
WARNING: CPU: 0 PID: 970 at drivers/gpu/drm/i915/intel_display.c:5615 intel_m...
Status: CLOSED DUPLICATE of bug 1342755
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-10 09:13 EDT by Stuart D Gathman
Modified: 2016-07-19 14:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 13:27:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stuart D Gathman 2015-08-10 09:13:36 EDT
Description of problem:
Kernel oops. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. reboot

Actual results:
kernel oops

Expected results:
clean boot

Additional info:
Even though this is a WARNING, it taints the kernel - so any subsequent kernel oops can't be reported.  For instance, a second later there is another kernel oops at intel_modeset_check_state that is tainted.  That second one means that putting the display to sleep crashes xorg (and therefore I have to disable this power saving feature on my laptop) - but I can't report it!!

This problem has been outstanding since f19.  There are some outstanding reports for f21 (search intel_modeset_check_state), and f21 and f19 reports deleted for EOL.  I'm reporting this *again* for f22 just to try to get the ball rolling.
Comment 1 Fedora End Of Life 2016-07-19 13:27:14 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 2 Stuart D Gathman 2016-07-19 14:33:10 EDT

*** This bug has been marked as a duplicate of bug 1342755 ***

Note You need to log in before you can comment on or make changes to this bug.