Bug 93666

Summary: [all] circular locking dependency detected: crtc_ww_class_mutex vs dev->mode_config.mutex
Product: DRI Reporter: Tomi Sarvela <tomi.p.sarvela>
Component: DRM/IntelAssignee: Matt Roper <matthew.d.roper>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: blocker    
Priority: highest CC: intel-gfx-bugs
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: BDW, HSW, ILK, IVB, SNB i915 features:
Attachments:
Description Flags
Serial log from deadlocked testhost none

Description Tomi Sarvela 2016-01-11 10:36:56 UTC
Created attachment 120953 [details]
Serial log from deadlocked testhost

One of the following commits caused i915 boot deadlock with kernel configuration:
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y

89d0d1b6f0e9c3a6b90476bd115cfe1881646fd6 drm-intel-nightly: 2016y-01m-06d-10h-37m-17s UTC integration manifest
d93c037246104e403436ffe339bcb832185d0627 drm/i915: Sanitize watermarks after hardware state readout (v4)
151268821e6f08956b28b6ff90fae187a5b230b8 drm/i915: Add extra paranoia to ILK watermark calculations
ee91a15972cc70efa4d17b4bbdb61ff314528110 drm/i915: Convert hsw_compute_linetime_wm to use in-flight state
0a8d8a8667c7e66f4fa2498be18d47f8b296b430 drm/i915: Setup clipped src/dest coordinates during FB reconstruction (v2)
c4e42196d47969a8b0df5eae734bc86c8df7cf44 drm-intel-nightly: 2016y-01m-06d-10h-07m-52s UTC integration manifest

Platforms affected:
ILK (HP Elitebook 8440p)
SNB (Lenovo X220 Tablet)
IVB (Lenovo T430s)
HSW (Brixbox, Gigabyte i5k with GT2, Dell XPS12)
BDW (Intel UltraBook, Intel NUC i7)
Comment 1 Maarten Lankhorst 2016-01-12 07:54:02 UTC
This will be fixed by the next version of

[PATCH] drm/i915: Handle error paths during watermark sanitization properly
Comment 2 Matt Roper 2016-01-12 19:14:37 UTC
The fix should be merged to di-nightly now; please re-open if there are still problems.

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.