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, 14 Apr 2021 08:48:58 +0200 [thread overview]
Message-ID: <66f5fdcb-d414-603d-bdb8-70579335b4a2@gmail.com> (raw)
In-Reply-To: <CABXGCsMMUa=0+GAHxfVdOOFO0Lx=tCa4+ongHN8rF4TAR9nVmg@mail.gmail.com>
Am 13.04.21 um 23:19 schrieb Mikhail Gavrilov:
> On Tue, 13 Apr 2021 at 12:29, Christian König <christian.koenig@amd.com> wrote:
>> Hi Mikhail,
>>
>> the crash is a known issue and should be fixed by:
>>
>> commit f63da9ae7584280582cbc834b20cc18bfb203b14
>> Author: Philip Yang <Philip.Yang@amd.com>
>> Date: Thu Apr 1 00:22:23 2021 -0400
>>
>> drm/amdgpu: reserve fence slot to update page table
>>
> Unfortunately, this commit couldn't fix the initial problem.
> 1. Result video is jerky if it grabbed and encoded with ffmpeg
> (h264_vaapi codec).
> 2. OBS still crashed if I try to record or stream video.
> 3. In the kernel log still appears the message "amdgpu: [mmhub] page
> fault (src_id:0 ring:0 vmid:4 pasid:32770, for process obs" if I tried
> to record or stream video by OBS.
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.
_______________________________________________
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-14 6:49 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 [this message]
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
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=66f5fdcb-d414-603d-bdb8-70579335b4a2@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;
as well as URLs for NNTP newsgroup(s).