[Bug 64431] New: [ivy bridge] intel_crtc_wait_for_pending_flips crash

[bugzilla-daemon at bugzilla.kernel.org]

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

            Bug ID: 64431
           Summary: [ivy bridge] intel_crtc_wait_for_pending_flips crash
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.12-rc1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: kam1kaz3 at gmail.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Today I left my computer for a couple of hours and I left my 2 screens on. When
I came back the monitors were in standby and I couldn't wake it up.
I logged in with another computer via SSH to find out what was wrong, and dmesg
had the following listed several times:

[368401.823959] INFO: task X:21291 blocked for more than 120 seconds.
[368401.823963]       Not tainted 3.12.0-1-dirty #1
[368401.823963] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[368401.823965] X               D ffff880210670c40     0 21291    309
0x00400000
[368401.823967]  ffff880105f13c48 0000000000000082 00000000000144c0
ffff880105f13fd8
[368401.823969]  ffff880105f13fd8 00000000000144c0 ffff880129eb0000
0000000000000000
[368401.823970]  0000000000000000 0000000000000000 0000000000000000
0000000000000000
[368401.823972] Call Trace:
[368401.823977]  [<ffffffff814e52e9>] schedule+0x29/0x70
[368401.823988]  [<ffffffffa07af3dd>]
intel_crtc_wait_for_pending_flips+0x8d/0x120 [i915]
[368401.823990]  [<ffffffff81084990>] ? wake_up_atomic_t+0x30/0x30
[368401.823995]  [<ffffffffa07b622f>] ironlake_crtc_disable+0x7f/0x930 [i915]
[368401.824000]  [<ffffffffa07bd9d7>] ? intel_modeset_check_state+0x477/0x780
[i915]
[368401.824005]  [<ffffffffa07ba43f>] intel_crtc_update_dpms+0x6f/0xa0 [i915]
[368401.824009]  [<ffffffffa07bdd22>] intel_connector_dpms+0x42/0x80 [i915]
[368401.824015]  [<ffffffffa0703ec8>]
drm_mode_obj_set_property_ioctl+0x308/0x320 [drm]
[368401.824018]  [<ffffffffa0703f10>]
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
[368401.824021]  [<ffffffffa06f2ef2>] drm_ioctl+0x522/0x650 [drm]
[368401.824025]  [<ffffffff811a0f42>] ? do_readv_writev+0x1a2/0x240
[368401.824028]  [<ffffffff81291254>] ? timerqueue_del+0x24/0x70
[368401.824029]  [<ffffffff81086bd6>] ? __remove_hrtimer+0x46/0xa0
[368401.824031]  [<ffffffff811b27d5>] do_vfs_ioctl+0x2e5/0x4d0
[368401.824033]  [<ffffffff8107083b>] ? recalc_sigpending+0x1b/0x50
[368401.824034]  [<ffffffff81071492>] ? __set_task_blocked+0x32/0x70
[368401.824036]  [<ffffffff811b2a41>] SyS_ioctl+0x81/0xa0
[368401.824038]  [<ffffffff814ee8dd>] system_call_fastpath+0x1a/0x1f

I had to soft reboot to have the screen turn on again. And this is not easily
reproducible...
I know the kernel isn't the most up to date one, but I'm posting the bug anyway
in case someone stumbles upon the same problem with other more recent kernels.

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