Bug 68134 - [SNB]igt/gem_suspend/fence-restore-untiled randomly causes call trace and *ERROR* stuck on bsd ring
Summary: [SNB]igt/gem_suspend/fence-restore-untiled randomly causes call trace and *ER...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 07:12 UTC by lu hua
Modified: 2017-10-06 14:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (111.18 KB, text/plain)
2013-08-15 07:12 UTC, lu hua
no flags Details
i915_error_state (2.09 MB, text/plain)
2013-08-15 07:13 UTC, lu hua
no flags Details
dmesg (102.90 KB, text/plain)
2013-08-19 05:43 UTC, lu hua
no flags Details
i915_error_state (2.09 MB, text/plain)
2013-08-19 06:41 UTC, lu hua
no flags Details

Description lu hua 2013-08-15 07:12:45 UTC
Created attachment 84087 [details]
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
Comment 1 lu hua 2013-08-15 07:13:14 UTC
Created attachment 84088 [details]
i915_error_state
Comment 2 Chris Wilson 2013-08-15 07:22:57 UTC
Looks like bug 64725 so please test https://bugs.freedesktop.org/attachment.cgi?id=83729
Comment 3 lu hua 2013-08-19 05:43:32 UTC
Created attachment 84225 [details]
dmesg

I test it on commit 884020b(include the patch). This issue still exists.
Comment 4 Daniel Vetter 2013-08-19 06:07:01 UTC
Can you please attach a new error state when running on the latest code?
Comment 5 lu hua 2013-08-19 06:41:37 UTC
Created attachment 84227 [details]
i915_error_state
Comment 6 Chris Wilson 2013-08-26 15:02:12 UTC
Hmm, still garbage in the BCS decoder. Can you please confirm this bug on -nightly?
Comment 7 lu hua 2013-08-27 02:23:07 UTC
(In reply to comment #6)
> Hmm, still garbage in the BCS decoder. Can you please confirm this bug on
> -nightly?


It doesn't happen on latest -nightly kernel.
Comment 8 lu hua 2013-08-28 03:25:21 UTC
It still happens on -fixes kernel.
Comment 9 Daniel Vetter 2013-08-28 09:08:43 UTC
The bugfix is in dinq/-nightly only. Too low real-world impact for -fixes. So please verify on -nightly only.
Comment 10 lu hua 2013-08-30 01:32:13 UTC
igt/gem_suspend/fence-restore-tiled2untiled also randomly causes  [drm:i915_hangcheck_elapsed] *ERROR* stuck on bsd ring on sandybridge with -fixes kernel.

I will close it if fixed on -fixes kernel.
Comment 11 lu hua 2013-09-17 01:38:30 UTC
Verified.Fixed.
Comment 12 Elizabeth 2017-10-06 14:44:04 UTC
Closing old verified.


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.