Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753742AbeAFQim (ORCPT + 1 other); Sat, 6 Jan 2018 11:38:42 -0500 Received: from mail-qk0-f169.google.com ([209.85.220.169]:45840 "EHLO mail-qk0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753520AbeAFQii (ORCPT ); Sat, 6 Jan 2018 11:38:38 -0500 X-Google-Smtp-Source: ACJfBosEds5JN2ZvnGtoa6yiRFJbHm9zH3uDMOcUiquQaIOqyBal+Ix1xioRFrEZr9lOaRVOfHztNQ== Date: Sat, 6 Jan 2018 11:38:35 -0500 From: Alexandru Chirvasitu To: Chris Wilson Cc: Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , intel-gfx@lists.freedesktop.org, kernel list Subject: Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5 Message-ID: <20180106163835.jknrwjt52nhbzzlt@D-69-91-141-110.dhcp4.washington.edu> References: <20180103163131.GD2118@chirva-void> <20180103215315.yf2hclzhxcie7qzn@D-69-91-141-110.dhcp4.washington.edu> <151517474548.6838.1821139419472614998@mail.alporthouse.com> <20180105193724.ghxzkcdm4cgiskmi@D-69-91-141-110.dhcp4.washington.edu> <151518186129.6838.5497512563650996948@mail.alporthouse.com> <20180105195842.zryxccc74k7fi6gq@D-69-91-141-110.dhcp4.washington.edu> <151518256891.6838.7870621097092357743@mail.alporthouse.com> <20180105220518.cmmof6rritm4bmjh@D-69-91-141-110.dhcp4.washington.edu> <151523540026.6838.8552050096058843898@mail.alporthouse.com> <20180106132443.yzn2pkfruu7basl7@D-69-91-141-110.dhcp4.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180106132443.yzn2pkfruu7basl7@D-69-91-141-110.dhcp4.washington.edu> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sat, Jan 06, 2018 at 08:24:43AM -0500, Alexandru Chirvasitu wrote: > Thank you! > > I'll apply that more elaborate patch you sent in the longer message to > my clone of the repo and see if it still freezes. > I'm on it now with no freezes yet, despite trying my best :). I have a question though: > On Sat, Jan 06, 2018 at 10:43:20AM +0000, Chris Wilson wrote: > > Quoting Alexandru Chirvasitu (2018-01-05 22:05:18) > > > Here we go. > > > > > > I have > > > > > > CONFIG_PAGE_POISONING not set > > > CONFIG_SLUB_STATS=y > > > CONFIG_SLUB_DEBUG not set > > > CONFIG_KASAN=y > > > > > > .config attached along as well for verification, in case I missed > > > anything. > > > > > > Again crashed by an attempt to open a terminal window. > > > > Gotcha, > > > > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c > > index b21322b50419..96cf46a10b4e 100644 > > --- a/drivers/gpu/drm/i915/i915_gem.c > > +++ b/drivers/gpu/drm/i915/i915_gem.c > > @@ -472,7 +472,7 @@ static void __fence_set_priority(struct dma_fence *fence, int prio) > > struct drm_i915_gem_request *rq; > > struct intel_engine_cs *engine; > > > > - if (!dma_fence_is_i915(fence)) > > + if (dma_fence_is_signaled(fence) || !dma_fence_is_i915(fence)) > > return; > > > > rq = to_request(fence); I went back to Linus' tree and compared the respective i915_gem.c files in the 4.14 and 4.15-rc6 commits. The offending piece of code seems to be in both, so I am wondering why I was not getting freezes before 4.15-rc. Is the other change (in drivers/gpu/drm/i915/intel_lrc.c) crucial too? The line GEM_BUG_ON(prio == I915_PRIORITY_INVALID); is caught by the diff, so that region of *that* file differs between 4.14 and 4.15-rc. I suppose it might also be that my distro's maintainers modify the 4.14 code in some fashion; I have not checked.