From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
amd-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch,
thomas.hellstrom@linux.intel.com,
LKML <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: Mon, 4 Apr 2022 10:22:31 +0200 [thread overview]
Message-ID: <f52945c8-92c2-7065-bd22-cb18c05bd76e@molgen.mpg.de> (raw)
In-Reply-To: <f3bc34e1-0eaf-84ef-486e-b7759e60b792@amd.com>
Dear Christian,
Am 04.04.22 um 08:30 schrieb Christian König:
> those are two independent and already known problems.
>
> The warning triggered from the sync_file is already fixed in
> drm-misc-next-fixes, but so far I couldn't figure out why the games
> suddenly doesn't work any more.
>
> There is a bug report for that, but bisecting the changes didn't yielded
> anything valuable so far.
>
> So if you can come up with something that would be rather valuable.
It’d be great, if you (or somebody else) could provide the URL to that
issue.
Kind regards,
Paul
next prev parent reply other threads:[~2022-04-04 8:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 18:39 Mikhail Gavrilov
2022-04-04 6:30 ` Christian König
2022-04-04 8:22 ` Paul Menzel [this message]
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
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=f52945c8-92c2-7065-bd22-cb18c05bd76e@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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
all inboxes | Powered by JetHome®