[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66f5fdcb-d414-603d-bdb8-70579335b4a2@gmail.com>
Date: Wed, 14 Apr 2021 08:48:58 +0200
From: Christian König <ckoenig.leichtzumerken@...il.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Christian König <christian.koenig@....com>
Cc: Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>
Subject: Re: [BUG] VAAPI encoder cause kernel panic if encoded video in 4K
Am 13.04.21 um 23:19 schrieb Mikhail Gavrilov:
> On Tue, 13 Apr 2021 at 12:29, Christian König <christian.koenig@....com> wrote:
>> Hi Mikhail,
>>
>> the crash is a known issue and should be fixed by:
>>
>> commit f63da9ae7584280582cbc834b20cc18bfb203b14
>> Author: Philip Yang <Philip.Yang@....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.
Powered by blists - more mailing lists