Bug 92187

Summary: check_crtc_state mismatch in ips_enabled on 4.2.1-1
Product: DRI Reporter: Henrik Jonsson <me>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
i915 call trace from kernel none

Description Henrik Jonsson 2015-09-30 07:27:58 UTC
Created attachment 118530 [details]
i915 call trace from kernel

Version of i915 (`pacman -Qi xf86-video-intel`): 1:2.99.917+381+g5772556-1
System architecture (`uname -m`): x86_64
Kernel version (`uname -r`): 4.2.1-1-ARCH
Linux distribution: Arch Linux
Machine: Lenovo Thinkpad X240
Display connector: VGA

After upgrading the Linux kernel yesterday, I noticed a delay when my laptop was resuming from hibernation. When looking at kernel logs, there was a i915 call trace from the kernel (see attachment) saying "mismatch in ips_enabled (expected 1, found 0)".

The graphics did recover after waiting ~10 sec or so, but I also noticed that my external monitor didn't get the mirrored image of my laptop, as it usually does. Closing the lid and opening it again fixed the issue with the external monitor (and I can't be sure it was caused by this issue).

The issue did not seem to be present on the previous version of the kernel I was running, 4.0.5-1-ARCH, but searching through kernel logs it's appeared six times since when I upgraded the kernel yesterday, often but not always associated with putting the laptop into hibernation.

Let me know how to provide more info, sorry about not having a full set of steps to repro the issue yet.
Comment 1 Henrik Jonsson 2015-09-30 07:56:33 UTC
Sorry about including the version of xf86-video-intel (xorg driver), I don't believe that's relevant since the logs indicate i915 in kernel space here.
Comment 2 Jani Nikula 2015-10-21 14:37:53 UTC

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

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.