All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
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: Wed, 11 May 2022 14:01:28 +0200	[thread overview]
Message-ID: <8e54ec49-09da-f345-35cd-430712f5a6ad@gmail.com> (raw)
In-Reply-To: <CABXGCsOqrB5zPFCeLw-VQjePikwDq4EKFQGc9hbOb5f7tGLDgg@mail.gmail.com>

Am 11.05.22 um 11:05 schrieb Mikhail Gavrilov:
> On Fri, Apr 15, 2022 at 1:04 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> 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.
> The message is just for history. The issue was fixed between
> b253435746d9a4a and 5.18rc4.

We have implemented a workaround, but still don't know the exact root cause.

If anybody wants to look into this it would be rather helpful to be able 
to reproduce the issue.

Regards,
Christian.

  reply	other threads:[~2022-05-11 12:01 UTC|newest]

Thread overview: 26+ 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:22     ` Paul Menzel
2022-04-04  8:38     ` Christian König
2022-04-04  8:38       ` Christian König
2022-04-08 11:01   ` Mikhail Gavrilov
2022-04-08 11:01     ` Mikhail Gavrilov
2022-04-08 11:13     ` Christian König
2022-04-08 11:13       ` Christian König
2022-04-08 12:24       ` Mikhail Gavrilov
2022-04-08 12:24         ` Mikhail Gavrilov
2022-04-08 14:27         ` Christian König
2022-04-08 14:27           ` Christian König
2022-04-08 17:25           ` Mikhail Gavrilov
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  5:38                 ` Mikhail Gavrilov
2022-04-15  8:04                 ` Christian König
2022-04-15  8:04                   ` Christian König
2022-05-11  9:05                   ` Mikhail Gavrilov
2022-05-11  9:05                     ` Mikhail Gavrilov
2022-05-11 12:01                     ` Christian König [this message]
2022-10-17 22:43                       ` Mikhail Gavrilov
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=8e54ec49-09da-f345-35cd-430712f5a6ad@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.