On Sat, 2 Feb 2019 at 10:20, Lyude Paul wrote:
>
> Atomic checks should never modify anything outside of the state that
> they're passed in. Unfortunately this appears to be exactly what we're
> doing in nv50_msto_atomic_check() where we update mstc->pbn every time
> the function is called. This
https://bugs.freedesktop.org/show_bug.cgi?id=100567
--- Comment #24 from ken...@gmail.com ---
Happened another 3 times.
Logs and stack traces:
- https://gist.github.com/kenorb/9e6537747630f72bf7cc4a5afcc288a7
- https://gist.github.com/kenorb/0e85a737488ad8c294d70dd83d2bcd13
-
https://bugs.freedesktop.org/show_bug.cgi?id=100446
Ilia Mirkin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Fri, Feb 01, 2019 at 07:20:03PM -0500, Lyude Paul wrote:
> Since
>
> commit 39b50c603878 ("drm/atomic_helper: Stop modesets on unregistered
> connectors harder")
>
> We've been failing atomic checks if they try to enable new displays on
> unregistered connectors. This is fine except for the
On Fri, Feb 01, 2019 at 05:41:58PM -0500, Lyude Paul wrote:
> Important! below
>
> On Fri, 2019-02-01 at 18:57 +0100, Daniel Vetter wrote:
> > On Thu, Jan 31, 2019 at 08:14:50PM -0500, Lyude Paul wrote:
> > > Since
> > >
> > > commit 39b50c603878 ("drm/atomic_helper: Stop modesets on