From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Mikhail Gavrilov" <mikhail.v.gavrilov@gmail.com>,
"Christian König" <christian.koenig@amd.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 13:47:15 +0200 [thread overview]
Message-ID: <e120f0a4-7600-c938-ac9f-cce6a714da4e@gmail.com> (raw)
In-Reply-To: <CABXGCsOQ8uXY85zrCOOd611gDj3AhtqH4=LcYHD=T9jVEzkuig@mail.gmail.com>
Am 15.09.21 um 12:36 schrieb Mikhail Gavrilov:
> On Wed, 15 Sept 2021 at 14:55, Christian König <christian.koenig@amd.com> wrote:
>> Yes, absolutely. You should see GPU resets and recovery in the system log after that.
> Unfortunately, not one DE will survive a GPU reset. All applications
> will terminate abnormally in fact this would be equivalent to reboot
> (and denial of service). :(
Yeah, very well known bug in the DEs.
The OpenGL robustness extension and Vulkan specification are pretty
clear what drivers are supposed to do in such a situation, it's just not
very well handled in userspace.
Regards,
Christian.
prev parent reply other threads:[~2021-09-15 11:47 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
2021-09-15 10:36 ` Mikhail Gavrilov
2021-09-15 11:47 ` Christian König [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=e120f0a4-7600-c938-ac9f-cce6a714da4e@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@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