From: "Christian König" <christian.koenig@amd.com>
To: "Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Cc: "Deucher, Alexander" <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@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: Thu, 14 Jan 2021 14:56:36 +0100 [thread overview]
Message-ID: <5f9e7752-68e8-aa5f-80ff-bb1196ea458d@amd.com> (raw)
In-Reply-To: <CABXGCsOcBMT4rL-bb4K_TzK70YmQsgNX37sHEHiqp_1kK1_UEQ@mail.gmail.com>
Am 14.01.21 um 01:22 schrieb Mikhail Gavrilov:
> On Tue, 12 Jan 2021 at 01:45, Christian König <christian.koenig@amd.com> wrote:
>> But what you have in your logs so far are only unrelated symptoms, the
>> root of the problem is that somebody is leaking memory.
>>
>> What you could do as well is to try to enable kmemleak
> I captured some memleaks.
> Do they contain any useful information?
Unfortunately not of hand.
I also don't see any bug reports from other people and can't reproduce
the last backtrace you send out TTM here.
Do you have any local modifications or special setup in your system?
Like bpf scripts or something like that?
Christian.
>
> [1] https://pastebin.com/n0FE7Hsu
> [2] https://pastebin.com/MUX55L1k
> [3] https://pastebin.com/a3FT7DVG
> [4] https://pastebin.com/1ALvJKz7
>
> --
> Best Regards,
> Mike Gavrilov.
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-01-14 13:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 22:26 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 [this message]
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
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=5f9e7752-68e8-aa5f-80ff-bb1196ea458d@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
/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
all inboxes | Powered by JetHome®