From: Leo Liu <leo.liu@amd.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "Christian König" <christian.koenig@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>
Subject: Re: [BUG] VAAPI encoder cause kernel panic if encoded video in 4K
Date: Tue, 13 Apr 2021 18:22:50 -0400 [thread overview]
Message-ID: <f253ff1f-3c5c-c785-1272-e4fe69a366ec@amd.com> (raw)
In-Reply-To: <CABXGCsM7z9Vmsh420MykJ8FzaCiSMWdSGCCvtYG2XrQKaw+SLQ@mail.gmail.com>
On 2021-04-13 5:24 p.m., Mikhail Gavrilov wrote:
> On Tue, 13 Apr 2021 at 04:55, Leo Liu <leo.liu@amd.com> wrote:
>>> It curious why ffmpeg does not cause such issues.
>>> For example such command not cause kernel panic:
>>> $ ffmpeg -f x11grab -framerate 60 -video_size 3840x2160 -i :0.0 -vf
>>> 'format=nv12,hwupload' -vaapi_device /dev/dri/renderD128 -vcodec
>>> h264_vaapi output3.mp4
>> What command are you using to see the issue or how can the issue be reproduced?
> $ mpv output4.mp4
This is decode command line, are you seeing issue with encode or
decode?, you also said `ffmpeg -f x11grab -framerate 60 -video_size
3840x2160 -i :0.0 -vf 'format=nv12,hwupload' -vaapi_device
/dev/dri/renderD128 -vcodec h264_vaapi output3.mp4` doesn't cause such
issue, right? What command line can cause the issue then?
>
> And of course, I know how it should works because when I encode video
> with CPU encoder (libx264) all fine.
> $ ffmpeg -f x11grab -framerate 60 -video_size 3840x2160 -i :0.0
> -vcodec libx264 output3.mp4
>
>> Please file a freedesktop gitlab issue, so we can keep track of it.
> Here? https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.freedesktop.org%2Fdrm%2Famd%2F-%2Fissues&data=04%7C01%7Cleo.liu%40amd.com%7C3cd466c3286e4303f2b108d8fec2833a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637539458675499474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=GbiA7%2FrkiLwh2E9js9tGhWkZyr%2B9TY57H6G6cL7ex8s%3D&reserved=0
Yes.
>
> Also, I found that other users face the same problem.
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbbs.archlinux.org%2Fviewtopic.php%3Fid%3D261965&data=04%7C01%7Cleo.liu%40amd.com%7C3cd466c3286e4303f2b108d8fec2833a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637539458675499474%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YNnk%2BZnPS0DVtuDfttnTThYfHOvmP38%2BwNpNZ5voLuk%3D&reserved=0
>
_______________________________________________
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-13 22:22 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 [this message]
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
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=f253ff1f-3c5c-c785-1272-e4fe69a366ec@amd.com \
--to=leo.liu@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--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