Re: REGRESSION: in intel video driver following introduction of mm_struct.has_pinned

2020-09-29 Thread Joonas Lahtinen
(+ intel-gfx for being i915 related) (+ Chris who has looked into the issue) Hi, Thanks for reporting! Could you open a bug report according to following instructions: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs A full dmesg of a bad boot and git bisect logs will be

Re: REGRESSION: in intel video driver following introduction of mm_struct.has_pinned

2020-09-29 Thread Chris Wilson
Quoting Joonas Lahtinen (2020-09-29 09:18:34) > (+ intel-gfx for being i915 related) > (+ Chris who has looked into the issue) > > Hi, > > Thanks for reporting! Fixed in commit a4d63c3732f1a0c91abcf5b7f32b4ef7dcd82025 Author: Jason A. Donenfeld Date: Mon Sep 28 12:35:07 2020 +0200 mm:

Re: REGRESSION: in intel video driver following introduction of mm_struct.has_pinned

2020-09-28 Thread Peter Xu
On Mon, Sep 28, 2020 at 02:14:16PM -0400, Tony Fischetti wrote: > After a length git bisection, I determined the commit that introduced > a change that ultimately caused a bug/oops null dereference (see below > for relevant syslog entries) was 008cfe4418b3dbda2ff.. (mm: Introduce >

REGRESSION: in intel video driver following introduction of mm_struct.has_pinned

2020-09-28 Thread Tony Fischetti
After a length git bisection, I determined the commit that introduced a change that ultimately caused a bug/oops null dereference (see below for relevant syslog entries) was 008cfe4418b3dbda2ff.. (mm: Introduce mm_struct.has_pinned) The RIP (according to syslog) occurs in function