On Fri, Jul 15, 2016 at 10:40 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > On Fri, Jul 15, 2016 at 08:00:25AM +0200, Sedat Dilek wrote: >> Hi, >> >> I see the below call-trace with latest d-i-n, guess latest linux-next >> will cause same issues. >> ( Beyond this, there exist also a build failure which me and Stephen >> have reported. ) >> The call-trace is reproducible with my setup and seen on every boot. >> >> Not sure if this is a problem in intel-gfx or fbdev. > > Personally, I blamed backlight, > https://patchwork.freedesktop.org/patch/95769/ [ CC Peter, Johannes and Thorsten "The regression reporter" ] Peter has 2 fixes from Johannes in peterz/queue.git#locking/urgent which fix the issue for me. [1/2] Revert "drm/fb-helper: Reduce READ_ONCE(master) to lockless_dereference" [2/2] locking/barriers: suppress sparse warnings in lockless_dereference() I tried today's Linus tree with those two fixes. Chris backlight fix is no more needed here. - Sedat - [1] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&id=f9d089b7830bbaa6ccaad29dff5fbb01d2a69945 [2] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&id=1804f7121995e8ca341427d848c0c8d267147720 _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
