From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Christian König" <christian.koenig@amd.com>,
airlied@linux.ie, daniel@ffwll.ch
Cc: nouveau@lists.freedesktop.org,
Alistair Popple <apopple@nvidia.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Corentin Labbe <clabbe.montjoie@gmail.com>,
bskeggs@redhat.com
Subject: Re: [Nouveau] nouveau: failed to initialise sync
Date: Wed, 14 Jul 2021 15:56:52 +0300 [thread overview]
Message-ID: <20210714125652.eohw2s2pncplxovx@box.shutemov.name> (raw)
In-Reply-To: <dace0dea-7ca9-99cb-ad80-106824cb5e3f@amd.com>
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
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2021-07-14 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 19:21 [Nouveau] nouveau: failed to initialise sync Corentin Labbe
2021-07-06 2:44 ` Alistair Popple
2021-07-06 6:58 ` Christian König
2021-07-06 7:42 ` Alistair Popple
2021-07-14 12:56 ` Kirill A. Shutemov [this message]
2021-07-14 13:02 ` Christian König
2021-07-14 15:02 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210714125652.eohw2s2pncplxovx@box.shutemov.name \
--to=kirill@shutemov.name \
--cc=airlied@linux.ie \
--cc=apopple@nvidia.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=clabbe.montjoie@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).