Date: Fri, 5 Jan 2018 15:08:49 -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: <20180105200849.ieqvrfl7vyd7b336@D-69-91-141-110.dhcp4.washington.edu>
References: <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>
 <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <151518256891.6838.7870621097092357743@mail.alporthouse.com>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org

Will do. 

On Fri, Jan 05, 2018 at 08:02:48PM +0000, Chris Wilson wrote:
> Quoting Alexandru Chirvasitu (2018-01-05 19:58:42)
> > OK, I then plan to try with the previous config, plus these
> > modifications:
> > 
> > CONFIG_PAGE_POISONING not set
> > CONFIG_SLUB_STATS=y
> > 
> > I'm a little puzzled about this:
> 
> [snip]
> 
> > > It would be CONFIG_SLUB_STATS and then you would a
> > > /sys/kernel/slab/i915_dependency/ directory with all the details of the
> > > slab, and in particular a poison file showing the status (and allowing
> > > it to modified) of slab poisoning
> > > 
> > > Ok, it looks like poisoning is only available if CONFIG_SLUB_DEBUG is
> > > set. Since it is not set, don't worry about it ;)
> > 
> > I actually do have SLUB_DEBUG set to 'y' in the kernel whose dmesg I
> > last sent you.
> 
> Ah, ok. I was looking at the config attached the first mail. Turn off
> SLUB_DEBUG for now to give ourselves the best chance at getting
> something from kasan. I hope it's worth the effort...

No worries, worth it at my end already. And thanks!

Will get back when I have another crash.