Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Jul 2021 15:56:52 +0300
From:   "Kirill A. Shutemov" <kirill@shutemov.name>
To:     Christian =?utf-8?B?S8O2bmln?= <christian.koenig@amd.com>,
        airlied@linux.ie, daniel@ffwll.ch
Cc:     Alistair Popple <apopple@nvidia.com>,
        Corentin Labbe <clabbe.montjoie@gmail.com>, bskeggs@redhat.com,
        dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
        linux-kernel@vger.kernel.org
Subject: Re: nouveau: failed to initialise sync
Message-ID: <20210714125652.eohw2s2pncplxovx@box.shutemov.name>
References: <YOC4uekpD7iA3xPi@Red>
 <1682547.0nLxAY2a9E@nvdebian>
 <dace0dea-7ca9-99cb-ad80-106824cb5e3f@amd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <dace0dea-7ca9-99cb-ad80-106824cb5e3f@amd.com>
Precedence: bulk

On Tue, Jul 06, 2021 at 08:58:37AM +0200, Christian K?nig wrote:
> Hi guys,
> 
> yes nouveau was using the same functionality for internal BOs without
> noticing it. This is fixes by the following commit:
> 
> commit d098775ed44021293b1962dea61efb19297b8d02
> Author: Christian K?nig <christian.koenig@amd.com>
> Date:?? Wed Jun 9 19:25:56 2021 +0200
> 
> ??? drm/nouveau: init the base GEM fields for internal BOs
> 
> ??? TTMs buffer objects are based on GEM objects for quite a while
> ??? and rely on initializing those fields before initializing the TTM BO.
> 
> ??? Nouveau now doesn't init the GEM object for internally allocated BOs,
> ??? so make sure that we at least initialize some necessary fields.
> 
> Could be that the patch needs to be send to stable as well.

The regression is present in v5.14-rc1. Any idea when it will hit
upstream? I don't see it being applied to drm=next.

-- 
 Kirill A. Shutemov