Might be though it's definitely a heisenbug since I zeroed in on that commit easily but now I can't reproduce it with 10+ cycles of loading/killing unigine-heaven On 07/16/2018 12:54 PM, Tom St Denis wrote: > > > On 07/16/2018 12:40 PM, Michel Dänzer wrote: >> On 2018-07-16 06:36 PM, Tom St Denis wrote: >>> Will in a bit. I'm tracking down a KASAN oops that the tip of drm-next >>> causes with unigine-heaven. >> >> Is it different from the one I reported an hour ago? >> >> https://lists.freedesktop.org/archives/amd-gfx/2018-July/024207.html >> >> > > Yes, my first bad commit is > > e9c9ce9b1a42362aee48b321cf7f0bb13db360e0 is the first bad commit > commit e9c9ce9b1a42362aee48b321cf7f0bb13db360e0 > Author: Christian König <christian.koenig at amd.com> > Date:  Fri Jul 13 16:29:10 2018 +0200 > >    drm/amdgpu: add amdgpu_job_submit_direct helper > >    Make sure that we properly initialize at least the sched member. > >    Signed-off-by: Christian König <christian.koenig at amd.com> >    Reviewed-by: Junwei Zhang <Jerry.Zhang at amd.com> >    Acked-by: Chunming Zhou <david1.zhou at amd.com> > > > I'll email a dmesg in a second in a new thread. > > Tom
