[Bug 94431] New: i915/intel_display.c check_crtc_state throws multiple warnings on resume from disk

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=94431

            Bug ID: 94431
           Summary: i915/intel_display.c check_crtc_state throws multiple
                    warnings on resume from disk
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.19.0 +
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: manuelkrause at netscape.net
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 169571
  --> https://bugzilla.kernel.org/attachment.cgi?id=169571&action=edit
dmesg for a 3.19.0

Hello,
my system is a HP Compaq 6730b notebook with "Integrated Graphics Chipset:
Intel(R) GM45" 
[    26.830] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[    26.910] (II) Module intel: vendor="X.Org Foundation"
[    26.910]     compiled for 1.17.0, module version = 2.99.917
[    26.910]     Module class: X.Org Video Driver
[    26.910]     ABI class: X.Org Video Driver, version 19.0
Using Kernel Mode Setting driver: i915, version 1.6.0 20141121 
(info from Xorg.0.log);
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
Kernel driver in use: i915
Kernel modules: i915 
(info from lspci)

Since kernel 3.19.0 I get multiple WARNINGs on each resume from suspend-to-disk
(hibernation). Suspend-to-RAM (sleep) is fine == without WARNING.
And I only get the WARNINGs -- there seem to be no problems at all.
Kernel 4.0.0-rc1 shows the same behaviour.

At first I'd attach the dmesg of a 3.19.0 and then of a 4.0.0-rc1 kernel.
BTW, the 3.19.0 is already patched with
f9b61ff6bce9a44555324b29e593fdffc9a115bc, to fix the related problem on here.

Please, let me know if you want me to /and how to generate additional debugging
output that you may need.

Best regards,
Manuel

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.