On Thu, Nov 20, 2014 at 02:34:12AM +0000, Zheng, Lv wrote: > Hi, > > > From: Kirill A. Shutemov [mailto:kir...@shutemov.name] > > Sent: Wednesday, November 19, 2014 8:16 PM > > > > On Tue, Nov 18, 2014 at 10:20:11PM +0100, Rafael J. Wysocki wrote: > > > On Tuesday, November 18, 2014 03:23:28 PM Kirill A. Shutemov wrote: > > > > On Wed, Nov 05, 2014 at 02:52:36AM +0000, Zheng, Lv wrote: > > > > > > [cut] > > > > > > > > > > > Here's lockdep warning I see on -next: > > > > > > Is patch [1/6] sufficient to trigger this or do you need all [1-4/6]? > > > > I only saw it on -next. I've tried to apply patches directly on -rc5 and > > don't see the warning. I don't have time for proper bisecting, sorry. > > Also I want to know if there is a real dead lock issue triggered?
I didn't see system hung or something. The laptop is usable at least. > I think we have worked the dead lock issue around to make it working even > when the fix is not merged so that we can have other EC work proceeded. > So maybe I only need to prevent the warning from being triggered at current > situation. > > Thanks and best regards > -Lv > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Kirill A. Shutemov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
