From: Wolfram Sang <wsa@kernel.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: amd-gfx@lists.freedesktop.org, linux-i2c@vger.kernel.org,
bibby.hsieh@mediatek.com
Subject: Re: Bug: amdgpu stutter and spam `Fence fallback timer expired` after suspend
Date: Thu, 6 Jan 2022 10:29:08 +0100 [thread overview]
Message-ID: <Yda2ZKhvclIxbrad@ninjato> (raw)
In-Reply-To: <7143a7147978f4104171072d9f5225d2ce355ec1.camel@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
> Should I send a revert, or is there a way to fix this?
You are the second one to report this problem and so far, there has been
no response from the authors. I will prepare a revert and CC all
involved people. Thank you for the nagging!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: linux-i2c@vger.kernel.org, bibby.hsieh@mediatek.com,
amd-gfx@lists.freedesktop.org
Subject: Re: Bug: amdgpu stutter and spam `Fence fallback timer expired` after suspend
Date: Thu, 6 Jan 2022 10:29:08 +0100 [thread overview]
Message-ID: <Yda2ZKhvclIxbrad@ninjato> (raw)
In-Reply-To: <7143a7147978f4104171072d9f5225d2ce355ec1.camel@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
> Should I send a revert, or is there a way to fix this?
You are the second one to report this problem and so far, there has been
no response from the authors. I will prepare a revert and CC all
involved people. Thank you for the nagging!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-06 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 21:26 Bug: amdgpu stutter and spam `Fence fallback timer expired` after suspend Konstantin Kharlamov
2022-01-05 21:33 ` Konstantin Kharlamov
2022-01-06 9:29 ` Wolfram Sang [this message]
2022-01-06 9:29 ` Wolfram Sang
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=Yda2ZKhvclIxbrad@ninjato \
--to=wsa@kernel.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bibby.hsieh@mediatek.com \
--cc=hi-angel@yandex.ru \
--cc=linux-i2c@vger.kernel.org \
/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.