All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Ken.Xue@amd.com, "Deucher, Alexander" <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	thomas.hellstrom@linux.intel.com,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.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: Fri, 8 Apr 2022 17:24:04 +0500	[thread overview]
Message-ID: <CABXGCsPi68Lyvg+6UjTK2aJm6PVBs83YJuP6x68mcrzAQgpuZg@mail.gmail.com> (raw)
In-Reply-To: <0d5f66d8-9852-b6a9-0e27-9eb9e736d698@amd.com>

On Fri, 8 Apr 2022 at 16:13, Christian König <christian.koenig@amd.com> wrote:

> I own you a beer.
>
> I still don't know what happens here, but that makes at least a bit more
> sense than a patch which only changes comments :)
>
> Looks like we are missing something here. Can I send you a patch to try
> something later today?

Yes, please feel free to send me a patch for testing.

-- 
Best Regards,
Mike Gavrilov.

WARNING: multiple messages have this Message-ID (diff)
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: 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, 8 Apr 2022 17:24:04 +0500	[thread overview]
Message-ID: <CABXGCsPi68Lyvg+6UjTK2aJm6PVBs83YJuP6x68mcrzAQgpuZg@mail.gmail.com> (raw)
In-Reply-To: <0d5f66d8-9852-b6a9-0e27-9eb9e736d698@amd.com>

On Fri, 8 Apr 2022 at 16:13, Christian König <christian.koenig@amd.com> wrote:

> I own you a beer.
>
> I still don't know what happens here, but that makes at least a bit more
> sense than a patch which only changes comments :)
>
> Looks like we are missing something here. Can I send you a patch to try
> something later today?

Yes, please feel free to send me a patch for testing.

-- 
Best Regards,
Mike Gavrilov.

  reply	other threads:[~2022-04-08 12:24 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 [this message]
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
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=CABXGCsPi68Lyvg+6UjTK2aJm6PVBs83YJuP6x68mcrzAQgpuZg@mail.gmail.com \
    --to=mikhail.v.gavrilov@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=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 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.