From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Harry Wentland <harry.wentland@amd.com>,
"Deucher, Alexander" <alexander.deucher@amd.com>
Subject: Re: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12
Date: Thu, 14 Jan 2021 05:22:37 +0500 [thread overview]
Message-ID: <CABXGCsOcBMT4rL-bb4K_TzK70YmQsgNX37sHEHiqp_1kK1_UEQ@mail.gmail.com> (raw)
In-Reply-To: <77b696b9-3248-d329-4f7d-5e27a21eabff@amd.com>
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?
[1] https://pastebin.com/n0FE7Hsu
[2] https://pastebin.com/MUX55L1k
[3] https://pastebin.com/a3FT7DVG
[4] https://pastebin.com/1ALvJKz7
--
Best Regards,
Mike Gavrilov.
WARNING: multiple messages have this Message-ID (diff)
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Deucher, Alexander" <alexander.deucher@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 05:22:37 +0500 [thread overview]
Message-ID: <CABXGCsOcBMT4rL-bb4K_TzK70YmQsgNX37sHEHiqp_1kK1_UEQ@mail.gmail.com> (raw)
In-Reply-To: <77b696b9-3248-d329-4f7d-5e27a21eabff@amd.com>
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?
[1] https://pastebin.com/n0FE7Hsu
[2] https://pastebin.com/MUX55L1k
[3] https://pastebin.com/a3FT7DVG
[4] https://pastebin.com/1ALvJKz7
--
Best Regards,
Mike Gavrilov.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "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 05:22:37 +0500 [thread overview]
Message-ID: <CABXGCsOcBMT4rL-bb4K_TzK70YmQsgNX37sHEHiqp_1kK1_UEQ@mail.gmail.com> (raw)
In-Reply-To: <77b696b9-3248-d329-4f7d-5e27a21eabff@amd.com>
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?
[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 0:33 UTC|newest]
Thread overview: 39+ 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-10 22:26 ` Mikhail Gavrilov
2021-01-10 22:26 ` Mikhail Gavrilov
2021-01-11 9:03 ` Christian König
2021-01-11 9:03 ` Christian König
2021-01-11 9:03 ` Christian König
2021-01-11 14:01 ` Christian König
2021-01-11 14:01 ` Christian König
2021-01-11 14:01 ` Christian König
2021-01-11 19:23 ` Mikhail Gavrilov
2021-01-11 19:23 ` Mikhail Gavrilov
2021-01-11 19:23 ` Mikhail Gavrilov
2021-01-11 20:45 ` Christian König
2021-01-11 20:45 ` Christian König
2021-01-11 20:45 ` Christian König
2021-01-11 21:51 ` Mikhail Gavrilov
2021-01-11 21:51 ` Mikhail Gavrilov
2021-01-11 21:51 ` Mikhail Gavrilov
2021-01-14 0:22 ` Mikhail Gavrilov [this message]
2021-01-14 0:22 ` Mikhail Gavrilov
2021-01-14 0:22 ` Mikhail Gavrilov
2021-01-14 13:56 ` Christian König
2021-01-14 13:56 ` Christian König
2021-01-14 13:56 ` Christian König
2021-01-14 14:06 ` Daniel Vetter
2021-01-14 14:06 ` Daniel Vetter
2021-01-14 14:06 ` Daniel Vetter
2021-01-14 22:43 ` Mikhail Gavrilov
2021-01-14 22:43 ` Mikhail Gavrilov
2021-01-14 22:43 ` Mikhail Gavrilov
2021-01-20 0:59 ` Mikhail Gavrilov
2021-01-20 0:59 ` Mikhail Gavrilov
2021-01-20 0:59 ` Mikhail Gavrilov
2021-01-21 13:27 ` Christian König
2021-01-21 13:27 ` Christian König
2021-01-21 13:27 ` Christian König
2021-01-25 5:28 ` Mikhail Gavrilov
2021-01-25 5:28 ` Mikhail Gavrilov
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=CABXGCsOcBMT4rL-bb4K_TzK70YmQsgNX37sHEHiqp_1kK1_UEQ@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=harry.wentland@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.