Date: Fri, 5 Jan 2018 14:37:24 -0500
From: Alexandru Chirvasitu <achirvasub@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
        Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>,
        intel-gfx@lists.freedesktop.org,
        kernel list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5
Message-ID: <20180105193724.ghxzkcdm4cgiskmi@D-69-91-141-110.dhcp4.washington.edu>
References: <151498375040.21495.10909014868670557680@mail.alporthouse.com>
 <20180103134642.GA2118@chirva-void>
 <151498727661.21495.7545852848027242671@mail.alporthouse.com>
 <20180103140340.GB2118@chirva-void>
 <151498852791.21495.13313443882665791372@mail.alporthouse.com>
 <20180103144826.GC2118@chirva-void>
 <151499122583.21495.1963140337943422469@mail.alporthouse.com>
 <20180103163131.GD2118@chirva-void>
 <20180103215315.yf2hclzhxcie7qzn@D-69-91-141-110.dhcp4.washington.edu>
 <151517474548.6838.1821139419472614998@mail.alporthouse.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <151517474548.6838.1821139419472614998@mail.alporthouse.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org

I'll try. I need a bit of clarification:

On Fri, Jan 05, 2018 at 05:52:25PM +0000, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-03 21:53:15)
> > All right, here's the dmesg from the kernel compiled from drm-tip (in
> > sync with upstream at the time of the compilation earlier today), with
> > 
> > CONFIG_DRM_I915_DEBUG_GEM=y
> > 
> > I crashed it by opening 20+ xterm windows. Doesn't always do it though
> > (tried this before).
> 
> Sorry, still stumped. It's still the same use-after-free and no asserts
> hit. Can you keep KASAN enabled but disable slab/page poisoning? Hmm, I
> think it has to be page poisoning doing the 0x6b as SLAB_POISON is
> disabled by default.

Would this have to be through a new compilation, or would it do to
just remove the poisoning kernel parameter on boot? 

> (You could check by enabling slabstats can looking in sysfs.)

Sorry, I was having some trouble parsing this; what do I check again
and how?

Does 'slabstats' refer to another kernel config option or something
else?

I apologize, most of these options I'm fiddling with are not familiar
to me..

> My goal is to get that kasan trace telling me who about the
> freed object.
> -Chris