From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12
Date: Mon, 25 Jan 2021 10:28:35 +0500 [thread overview]
Message-ID: <CABXGCsOhn_2xg=HcZ3b=nuWhmBGF5Xz7WuLHORVZ-DV=eZQTPQ@mail.gmail.com> (raw)
In-Reply-To: <bb671243-7031-31ff-c6c3-dc1e4192ef71@amd.com>
On Thu, 21 Jan 2021 at 18:27, Christian König <christian.koenig@amd.com> wrote:
>
> I still have no idea what's going on here.
>
> The KASAN messages from the DC code are completely unrelated.
>
> Please add the full dmesg to your bug report.
>
I did it.
https://gitlab.freedesktop.org/drm/amd/-/issues/1439#note_776267
--
Best Regards,
Mike Gavrilov.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-01-25 5:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 22:26 [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12 Mikhail Gavrilov
2021-01-11 9:03 ` Christian König
2021-01-11 14:01 ` Christian König
2021-01-11 19:23 ` Mikhail Gavrilov
2021-01-11 20:45 ` Christian König
2021-01-11 21:51 ` Mikhail Gavrilov
2021-01-14 0:22 ` Mikhail Gavrilov
2021-01-14 13:56 ` Christian König
2021-01-14 14:06 ` Daniel Vetter
2021-01-14 22:43 ` Mikhail Gavrilov
2021-01-20 0:59 ` Mikhail Gavrilov
2021-01-21 13:27 ` Christian König
2021-01-25 5:28 ` Mikhail Gavrilov [this message]
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='CABXGCsOhn_2xg=HcZ3b=nuWhmBGF5Xz7WuLHORVZ-DV=eZQTPQ@mail.gmail.com' \
--to=mikhail.v.gavrilov@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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).