[Bug 68134] New: [SNB]igt/gem_suspend/fence-restore-untiled randomly causes call trace and *ERROR* stuck on bsd ring

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 68134
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [SNB]igt/gem_suspend/fence-restore-untiled randomly
                    causes call trace and *ERROR* stuck on bsd ring
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: huax.lu at intel.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 84087
  --> https://bugs.freedesktop.org/attachment.cgi?id=84087&action=edit
dmesg

System Environment:
--------------------------
Platform:    Sandybridge
Kernel:     (drm-intel-fixes)3d51af04567800a87a04785d375f1258977ef6d7

Bug detailed description:
-----------------------------
It randomly causes call trace and [drm:i915_hangcheck_elapsed] *ERROR* stuck on
bsd ring. It happens 1 in 5 runs on sandybridge with -fixes kernel.
I run it 5 cycles on -nightly branch, It works well.

output:
rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Aug 15 06:31:58 2013
checking the first canary object
checking the second canary object
Subtest fence-restore-untiled: SUCCESS


Call Trace:
[   29.611097]  [<ffffffff816ed7b8>] ? dump_stack+0x41/0x51
[   29.611102]  [<ffffffffa01932a6>] ? read_phy_reg+0x71/0x82 [firewire_ohci]
[   29.611104]  [<ffffffffa01954b9>] ? ohci_enable+0x26f/0x535 [firewire_ohci]
[   29.611106]  [<ffffffff812e26dd>] ? pci_pm_restore+0x7b/0x7b
[   29.611108]  [<ffffffffa019580e>] ? pci_resume+0x8f/0x116 [firewire_ohci]
[   29.611110]  [<ffffffff812e26dd>] ? pci_pm_restore+0x7b/0x7b
[   29.611113]  [<ffffffff81368ba3>] ? dpm_run_callback.isra.11+0x24/0x52
[   29.611114]  [<ffffffff813696f3>] ? device_resume+0x109/0x14a
[   29.611116]  [<ffffffff81369748>] ? async_resume+0x14/0x38
[   29.611117]  [<ffffffff8104d3d7>] ? async_run_entry_fn+0x55/0x10b
[   29.611119]  [<ffffffff8104388c>] ? process_one_work+0x1c5/0x2df
[   29.611120]  [<ffffffff81043de3>] ? worker_thread+0x1c7/0x2bc
[   29.611122]  [<ffffffff81043c1c>] ? rescuer_thread+0x251/0x251
[   29.611124]  [<ffffffff810487a2>] ? kthread+0xad/0xb5
[   29.611126]  [<ffffffff810486f5>] ? kthread_freezable_should_stop+0x40/0x40
[   29.611128]  [<ffffffff816f7f2c>] ? ret_from_fork+0x7c/0xb0
[   29.611130]  [<ffffffff810486f5>] ? kthread_freezable_should_stop+0x40/0x40
[   29.611133] dpm_run_callback(): pci_pm_resume+0x0/0x7b returns -16
[   29.611134] PM: Device 0000:04:03.0 failed to resume async: error -16


Reproduce steps:
----------------------------
1. ./gem_suspend --run-subtest fence-restore-untiled

-- 
You are receiving this mail because:
You are the QA Contact 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/20130815/b9709b99/attachment.html>