From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "Christian König" <christian.koenig@amd.com>,
thomas.hellstrom@linux.intel.com,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Deucher, Alexander" <alexander.deucher@amd.com>,
Ken.Xue@amd.com
Subject: Re: [Bug][5.18-rc0] Between commits ed4643521e6a and 34af78c4e616, appears warning "WARNING: CPU: 31 PID: 51848 at drivers/dma-buf/dma-fence-array.c:191 dma_fence_array_create+0x101/0x120" and some games stopped working.
Date: Fri, 15 Apr 2022 10:04:06 +0200 [thread overview]
Message-ID: <675a2d33-b286-d1d0-e4e7-05d6516026c0@gmail.com> (raw)
In-Reply-To: <CABXGCsP19VFRgTx5yGn68iCK3NxPxi_b9MTq=AmHtFPv9xR5sA@mail.gmail.com>
Am 15.04.22 um 07:38 schrieb Mikhail Gavrilov:
> On Sat, Apr 9, 2022 at 7:27 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> That's unfortunately not the end of the story.
>>
>> This is fixing your problem, but reintroducing the original problem that
>> we call the syncobj with a lock held which can crash badly as well.
>>
>> Going to take a closer look on Monday. I hope you can test a few more
>> patches to help narrow down what's actually going wrong here.
>>
>> Thanks,
>> Christian.
>>
> Hi Christian.
> I'm sorry to trouble you.
> Have you forgotten about this issue?
>
No, I just couldn't find time during all that bug fixing :)
Sorry for the delay, going to take a look after the eastern holiday here.
Christian.
next prev parent reply other threads:[~2022-04-15 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 18:39 [Bug][5.18-rc0] Between commits ed4643521e6a and 34af78c4e616, appears warning "WARNING: CPU: 31 PID: 51848 at drivers/dma-buf/dma-fence-array.c:191 dma_fence_array_create+0x101/0x120" and some games stopped working Mikhail Gavrilov
2022-04-04 6:30 ` Christian König
2022-04-04 8:22 ` Paul Menzel
2022-04-04 8:38 ` Christian König
2022-04-08 11:01 ` Mikhail Gavrilov
2022-04-08 11:13 ` Christian König
2022-04-08 12:24 ` Mikhail Gavrilov
2022-04-08 14:27 ` Christian König
2022-04-08 17:25 ` Mikhail Gavrilov
2022-04-09 14:27 ` Christian König
2022-04-15 5:38 ` Mikhail Gavrilov
2022-04-15 8:04 ` Christian König [this message]
2022-05-11 9:05 ` Mikhail Gavrilov
2022-05-11 12:01 ` Christian König
2022-10-17 22:43 ` Mikhail Gavrilov
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=675a2d33-b286-d1d0-e4e7-05d6516026c0@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Ken.Xue@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=thomas.hellstrom@linux.intel.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