From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>
Subject: Re: [BUG] VAAPI encoder cause kernel panic if encoded video in 4K
Date: Wed, 21 Apr 2021 18:58:50 +0500 [thread overview]
Message-ID: <CABXGCsN_ZsQpeFOpkdJyn_JtG1imp4+Yrfr2msqQGUwNDoLpmg@mail.gmail.com> (raw)
In-Reply-To: <fff4926a-8f20-8d31-611b-473e84d89af0@amd.com>
On Wed, 21 Apr 2021 at 11:42, Christian König <christian.koenig@amd.com> wrote:
> I can try, but I'm not sure if we even have the full page fault handling
> for Navi in 5.12.
>
It would be great. For me this patch is working as expected and I
already for several days didn't see the panic "kernel BUG at
drivers/dma-buf/dma-resv.c:287!".
Anyway I will waiting for any news.
--
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-04-21 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 22:05 [BUG] VAAPI encoder cause kernel panic if encoded video in 4K Mikhail Gavrilov
2021-04-12 23:55 ` Leo Liu
2021-04-13 21:24 ` Mikhail Gavrilov
2021-04-13 22:22 ` Leo Liu
2021-04-14 23:10 ` Mikhail Gavrilov
2021-04-13 7:29 ` Christian König
2021-04-13 21:19 ` Mikhail Gavrilov
2021-04-14 6:48 ` Christian König
2021-04-20 18:03 ` Mikhail Gavrilov
2021-04-21 6:42 ` Christian König
2021-04-21 13:58 ` Mikhail Gavrilov [this message]
2021-09-14 18:19 ` Mikhail Gavrilov
2021-09-15 9:55 ` Christian König
2021-09-15 10:36 ` Mikhail Gavrilov
2021-09-15 11:47 ` Christian König
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=CABXGCsN_ZsQpeFOpkdJyn_JtG1imp4+Yrfr2msqQGUwNDoLpmg@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.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 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).