[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1608021448340.22028@cbobk.fhfr.pm>
Date: Tue, 2 Aug 2016 14:49:11 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Jani Nikula <jani.nikula@...ux.intel.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel.vetter@...el.com>,
DRI mailing list <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: [git pull] drm for v4.8
On Tue, 2 Aug 2016, Jani Nikula wrote:
> >> > This is the main drm pull request for 4.8, I'm down with a cold at the moment
> >> > so hopefully this isn't in too bad a state, I finished pulling stuff last
> >> > week mostly (nouveau fixes just went in today), so only this message should
> >> > be influenced by illness. Apologies to anyone who's major feature I missed :-)
> >> >
> >> > i915:
> >> > BXT support enabled by default
> >> > GVT-g infrastructure
> >> > GuC command submission and fixes
> >> > BXT workarounds
> >> > SKL/BKL workarounds
> >> > Demidlayering device registration
> >> > Thundering herd fixes
> >> > Missing pci ids
> >> > Atomic updates
> >>
> >> Hmm. I did the merge and pushed it out, but testing it on my laptop
> >> shows some very annoying flickering problem.
> >
> > In addition to that, what I see with current git (HEAD == 731c7d3a205,
> > i.e. the drm merge) is lockdep report during bootup about AB-BA between
> > mode_config.mutex and fb_notifier_list rwsem; will probably not have time
> > to look into it more (look at the code and / or bisect) until tomorrow, so
> > sending out early as a heads-up.
> >
> > Also, trying to suspend the machine to disk hangs, with the "suspend" LED
> > constantly blinking, LCD being blank, but the machine never actually
> > powering off. Not sure whether it might not be the very deadlock actually
> > triggering for real.
>
> There was [1] before my vacation to fix this, but it doesn't seem to
> have gone anywhere since. And it doesn't refer what caused the lockdep
> splat to begin with.
Confirmed, that patch fixes the lockdep splat, so for that part
Tested-by: Jiri Kosina <jkosina@...e.cz>
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists