From: "Christian König" <christian.koenig@amd.com>
To: "Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: 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, 15 Sep 2021 11:55:51 +0200 [thread overview]
Message-ID: <dcbb87cc-c95d-ae58-d601-413a6277a7f8@amd.com> (raw)
In-Reply-To: <CABXGCsOPLH2DkZ09PDXSxStin6JJb_m5bJuQWmXooBLaSJ2Ezg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Am 14.09.21 um 20:19 schrieb Mikhail Gavrilov:
> On Wed, 14 Apr 2021 at 11:48, Christian König
> <ckoenig.leichtzumerken@gmail.com
> <mailto:ckoenig.leichtzumerken@gmail.com>> wrote:
>
>
> That is expected behavior, the application is just buggy and
> causing a
> page fault on the GPU.
>
> The kernel should just not crash with a backtrace.
>
> Regards,
> Christian.
>
>
> If after it GPU hangs with the message
> "[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for
> fences timed out!" is it also expected behavior?
Yes, absolutely. You should see GPU resets and recovery in the system
log after that.
Regards,
Christian.
> Kernel log: https://pastebin.com/WkhATKXX
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpastebin.com%2FWkhATKXX&data=04%7C01%7Cchristian.koenig%40amd.com%7C83d3316107ce4c9fe42a08d977ac2ea3%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637672405000225872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BSCdZefdxpQPBdKzrcII8e9LDR8nN%2BbMkswE%2FEkaXv8%3D&reserved=0>
>
>
> --
> Best Regards,
> Mike Gavrilov.
[-- Attachment #2: Type: text/html, Size: 3396 bytes --]
next prev parent reply other threads:[~2021-09-15 9:56 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
2021-09-14 18:19 ` Mikhail Gavrilov
2021-09-15 9:55 ` Christian König [this message]
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=dcbb87cc-c95d-ae58-d601-413a6277a7f8@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.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