[Bug 88654] [BYT/BDW bisected]igt/pm_rps/reset sporadically causes system hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Feb 1 22:07:13 PST 2015


https://bugs.freedesktop.org/show_bug.cgi?id=88654

Ding Heng <hengx.ding at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[BDW]igt/pm_rps/reset       |[BYT/BDW
                   |sporadically causes system  |bisected]igt/pm_rps/reset
                   |hang                        |sporadically causes system
                   |                            |hang

--- Comment #1 from Ding Heng <hengx.ding at intel.com> ---
b8d24a06568368076ebd5a858a011699a97bfa42 is the first bad commit.
commit b8d24a06568368076ebd5a858a011699a97bfa42
Author:     Mika Kuoppala <mika.kuoppala at linux.intel.com>
AuthorDate: Wed Jan 28 17:03:14 2015 +0200
Commit:     Daniel Vetter <daniel.vetter at ffwll.ch>
CommitDate: Thu Jan 29 18:03:07 2015 +0100

    drm/i915: Remove nested work in gpu error handling

    Now when we declare gpu errors only through our own dedicated
    hangcheck workqueue there is no need to have a separate workqueue
    for handling the resetting and waking up the clients as the deadlock
    concerns are no more.

    The only exception is i915_debugfs::i915_set_wedged, which triggers
    error handling through process context. However as this is only used
through
    test harness it is responsibility for test harness not to introduce hangs
    through both debug interface and through hangcheck mechanism at the same
time.

    Remove gpu_error.work and let the hangcheck work do the tasks it used to.

    v2: Add a big warning sign into i915_debugfs::i915_set_wedged (Chris)

    Cc: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Mika Kuoppala <mika.kuoppala at intel.com>
    Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150202/fa0f3c35/attachment.html>


More information about the intel-gfx-bugs mailing list