| Summary: | [BDW] igt@kms_busy@extended-pageflip-hang-newfb-default-A hard hang | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| Component: | DRM/Intel | Assignee: | Marta Löfstedt <marta.lofstedt> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BDW | i915 features: | display/Other |
|
Description
Marta Löfstedt
2017-05-30 10:32:45 UTC
reproduced on HSW Harrisbeach drm-tip: commit d4bedb8b0f9ba91df2e8cb136a489145a83e96a7 Author: Sean Paul <seanpaul@chromium.org> Date: Tue Jun 13 10:23:36 2017 -0400 drm-tip: 2017y-06m-13d-14h-22m-46s UTC integration manifest Maarten believes this is a duplicate of bug 99093. I can reproduce this hard hang 100% on BDW NUCi5 and Harrisbeach HSW. *** This bug has been marked as a duplicate of bug 99093 *** Since Chris now has a workaround for the PNV hang in: https://bugs.freedesktop.org/show_bug.cgi?id=99093 which doesn't fix this issue. I will un-duplicate this bug and continue working on it. tested some of the kms_busy --run-subtest extended-* with Villes branch: git://github.com/vsyrjala/linux.git no_commit_reordering Still hit some deadlock: [ 1450.965818] INFO: task kworker/2:3:2643 blocked for more than 120 seconds. [ 1450.965827] Tainted: G U 4.12.0-rc4+ #2 [ 1450.965830] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1450.965833] kworker/2:3 D 0 2643 2 0x00000000 [ 1450.965924] Workqueue: events_long i915_hangcheck_elapsed [i915] [ 1450.965927] Call Trace: [ 1450.965939] __schedule+0x3c4/0x820 [ 1450.965946] schedule+0x36/0x80 [ 1450.965951] schedule_preempt_disabled+0xe/0x10 [ 1450.965956] __ww_mutex_lock.isra.6+0x3de/0x6b0 [ 1450.965963] __ww_mutex_lock_slowpath+0x16/0x20 [ 1450.965968] ? __ww_mutex_lock_slowpath+0x16/0x20 [ 1450.965973] ww_mutex_lock+0x37/0x70 [ 1450.966009] modeset_backoff+0x4b/0xc0 [drm] [ 1450.966039] drm_modeset_backoff+0x10/0x20 [drm] [ 1450.966118] intel_prepare_reset+0x4e/0xe0 [i915] [ 1450.966171] i915_reset_and_wakeup+0xad/0x190 [i915] [ 1450.966224] i915_handle_error+0x1df/0x220 [i915] [ 1450.966229] ? scnprintf+0x49/0x80 [ 1450.966298] hangcheck_declare_hang+0xe2/0x110 [i915] [ 1450.966363] ? gen6_read32+0x9f/0x1c0 [i915] [ 1450.966424] i915_hangcheck_elapsed+0x29f/0x2d0 [i915] [ 1450.966430] process_one_work+0x1e9/0x3f0 [ 1450.966433] worker_thread+0x4b/0x410 [ 1450.966439] kthread+0x109/0x140 [ 1450.966443] ? process_one_work+0x3f0/0x3f0 [ 1450.966448] ? kthread_create_on_node+0x70/0x70 [ 1450.966452] ret_from_fork+0x25/0x30 [ 1450.966456] NMI backtrace for cpu 0 [ 1450.966461] CPU: 0 PID: 36 Comm: khungtaskd Tainted: G U 4.12.0-rc4+ #2 [ 1450.966463] Hardware name: /NUC5i5RYB, BIOS RYBDWi35.86A.0249.2015.0529.1640 05/29/2015 [ 1450.966465] Call Trace: [ 1450.966470] dump_stack+0x63/0x8d [ 1450.966475] nmi_cpu_backtrace+0x94/0xa0 [ 1450.966479] ? irq_force_complete_move+0x140/0x140 [ 1450.966484] nmi_trigger_cpumask_backtrace+0xde/0x110 Note: that Maarten now has an IGT patch where the bad behvior of the igt@kms_busy@extended-* tests no longer appear reproducible: commit 9120ee572f86ed6f3da088187043785d1da340c9 Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Date: Wed Jun 28 12:49:35 2017 +0200 tests/kms_busy: Remove gem_bo_busy checks On the other hand Ville is still working with the real fix in the drive I was to optimistic on the impact of Maartens IGT patch. After running all kms test during the night the same issue was reproduced. I can't reproduce this issue on BDW drm-tip 4.13.0-rc2+ git@f9cb5a18. However, the tests are now skipped. I can no longer reproduce this issue. Most likely fixed by the following commit: commit c4bbb7358425b3a1c93f4d8c12a8fe46438ca73b Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Date: Tue Jul 11 16:33:14 2017 +0200 drm/atomic: Allow drm_atomic_helper_swap_state to fail |
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.