Bug 1251994 - WARNING: CPU: 0 PID: 970 at drivers/gpu/drm/i915/intel_display.c:5615 intel_modeset_check_state+0xaec/0xc60 [i915]()
Summary: WARNING: CPU: 0 PID: 970 at drivers/gpu/drm/i915/intel_display.c:5615 intel_m...
Keywords:
Status: CLOSED DUPLICATE of bug 1342755
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-10 13:13 UTC by Stuart D Gathman
Modified: 2016-07-19 18:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 17:27:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stuart D Gathman 2015-08-10 13:13:36 UTC
Description of problem:
Kernel oops. 

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-12.20150615.fc22.i686
kernel-4.1.3-201.fc22.i686

How reproducible:
always

Steps to Reproduce:
1. reboot
2.
3.

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 17:27:14 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 Stuart D Gathman 2016-07-19 18:33:10 UTC

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