[Bug 93666] New: CONFIG_DEBUG_*MUTEX* causes i915 deadlock on several platforms
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Jan 11 02:36:56 PST 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93666
Bug ID: 93666
Summary: CONFIG_DEBUG_*MUTEX* causes i915 deadlock on several
platforms
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: tomi.p.sarvela at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 120953
--> https://bugs.freedesktop.org/attachment.cgi?id=120953&action=edit
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)
--
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/20160111/07a21217/attachment.html>
More information about the intel-gfx-bugs
mailing list