Red Hat Bugzilla – Bug 1010116
WARNING: CPU: 0 PID: 96 at drivers/gpu/drm/i915/intel_display.c:8286 check_crtc_state+0x590/0xb30 [i915]()
Last modified: 2015-02-17 12:15:40 EST
Created attachment 800269 [details]
Call trace that was written to /var/log/messages.
Description of problem:
Starting with kernel version kernel-PAE-3.11.1-200.fc19.i686, a stack trace is generated in /var/log/messages.
Version-Release number of selected component (if applicable):
rpm -q kernel-PAE xorg-x11-drv-intel xorg-x11-server-Xorg
Each time that kernel-PAE-3.11.1-200 is started. The problem does not appear if the previous kernel, version kernel-PAE-3.10.11, is started.
Steps to Reproduce:
1. Boot the operating system, selecting kernel version kernel-PAE-3.11.1
2. When the booting process has completed, the warning message is found in /var/log/messages.
See the attached trace [text file].
No trace should be generated by xorg-x11-drv-intel.
can we get a full /var/log/Xorg.0.log?
Actually booting with drm.debug=0xe and then grabbing the full dmesg is usually sufficient to reconstruct what went wrong with the drm/i915 modeset state tracking. But I have an idea and will attach a quick patch shortly.
Created attachment 800340 [details]
fixup lvds border bits readout (hopefully)
Please test the attached patch.
has a scratch build to test.
(In reply to Dave Airlie from comment #1)
> can we get a full /var/log/Xorg.0.log?
Please find a copy of this requested file in the attachments.
Created attachment 800840 [details]
Copy of /var/log/Xorg.0.log
(In reply to Daniel Vetter from comment #2)
> Actually booting with drm.debug=0xe and then grabbing the full dmesg is
> usually sufficient to reconstruct what went wrong with the drm/i915 modeset
> state tracking. But I have an idea and will attach a quick patch shortly.
In case it is of some use, a copy of the output of dmesg (after booting with drm.debug=0xe added to the kernel parameters) is included as an attachment.
Created attachment 800841 [details]
Copy of the output of dmesg after booting with drm.debug=0xe added to the kernel parameters
This problem persists with kernel version 3.4.11-201.fc19.i686.PAE.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.