Re: ✗ Fi.CI.BAT: failure for drm/i915: Propagate error from drm_gem_object_init() (rev2)

From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Propagate error from drm_gem_object_init() (rev2)
Date: Thu, 28 Apr 2016 09:15:21 +0300	[thread overview]
Message-ID: <1461824121.3612.1.camel@linux.intel.com> (raw)
In-Reply-To: <20160427134455.GF27856@nuc-i3427.alporthouse.com>

On ke, 2016-04-27 at 14:44 +0100, Chris Wilson wrote:
> On Wed, Apr 27, 2016 at 04:35:33PM +0300, Joonas Lahtinen wrote:
> > 
> > On ma, 2016-04-25 at 13:24 +0000, Patchwork wrote:
> > > 
> > > == Series Details ==
> > > 
> > > Series: drm/i915: Propagate error from drm_gem_object_init() (rev2)
> > > URL   : https://patchwork.freedesktop.org/series/6149/
> > > State : failure
> > > 
> > > == Summary ==
> > > 
> > > Series 6149v2 drm/i915: Propagate error from drm_gem_object_init()
> > > http://patchwork.freedesktop.org/api/1.0/series/6149/revisions/2/mbox/
> > > 
> > > Test drv_module_reload_basic:
> > >                 pass       -> DMESG-WARN (ilk-hp8440p)
> > This seems like a problem that has not previously appeared. Please give
> > it a look.
> >  	
> > [  474.322285] =============================================================================
> > [  474.322294] BUG dentry(4:session-c1.scope) (Tainted: G     U         ): Redzone overwritten
> > [  474.322299] -----------------------------------------------------------------------------
> > 
> > [  474.322304] Disabling lock debugging due to kernel taint
> > [  474.322306] INFO: 0xffff8800b561f0c0-0xffff8800b561f0c3. First byte 0x0 instead of 0xcc
> > [  474.322316] INFO: Allocated in __d_alloc+0x20/0x1b0 age=3579 cpu=3 pid=6426
> > [  474.322323] 	___slab_alloc.constprop.62+0x37c/0x3b0
> > [  474.322327] 	__slab_alloc.isra.59.constprop.61+0x43/0x80
> > [  474.322331] 	kmem_cache_alloc+0x259/0x300
> > [  474.322334] 	__d_alloc+0x20/0x1b0
> > [  474.322337] 	d_alloc+0x18/0x70
> > [  474.322342] 	__lookup_hash+0x2e/0x50
> > [  474.322344] 	lookup_one_len+0xcd/0x120
> > [  474.322350] 	start_creating+0x71/0x100
> > [  474.322353] 	debugfs_create_file+0x2e/0xe0
> > [  474.322396] 	i915_debugfs_init+0xc8/0x120 [i915]
> > [  474.322401] 	drm_debugfs_init+0xa3/0x130
> > [  474.322405] 	drm_minor_register+0x5a/0x110
> > [  474.322411] 	drm_dev_register+0x2a/0xb0
> > [  474.322416] 	drm_get_pci_dev+0xce/0x1e0
> > [  474.322431] 	i915_pci_probe+0x2f/0x50 [i915]
> > [  474.322437] 	pci_device_probe+0x87/0xf0
> > [  474.322442] INFO: Slab 0xffffea0002d58700 objects=26 used=14 fp=0xffff8800b561cc38 flags=0x4000000000004081
> > [  474.322451] INFO: Object 0xffff8800b561f0c8 @offset=12488 fp=0xffff8800b561ee58
> [  474.322463] Redzone ffff8800b561f0c0: 00 f0 ff ff cc cc cc cc ........
> 
> -> 255.255.240.0
> 
> I don't this is ours. A pass through with kasan / kmemcheck would still
> be good to rule it out.

Tomi ran another run of BAT on ILK, and it was all success.

Was kasan/kmemcheck run done?

Regards, Joonas

> -Chris
> 
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx