From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"Wentland, Harry" <harry.wentland@amd.com>,
Dave Airlie <airlied@gmail.com>,
"Koenig, Christian" <christian.koenig@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Mon, 10 Jan 2022 17:21:09 -0800 [thread overview]
Message-ID: <CAHk-=wiCCRG9Lwzr+Cur=K1V2GJ9ab_ket7EnG4RZhJ8jJM7xQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_OYO7kq+9DBnDvbSfpouFvdLB0LPSL6+f1ZPRBsV=qEqA@mail.gmail.com>
On Mon, Jan 10, 2022 at 5:11 PM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> We are putting together a system to try and repro the issue. Does it
> happen with a single monitor or only with two?
Nope. With a single monitor everything seems to look fine. And when I
plug in the second monitor, it immediately starts happening again.
It also seems to depend a bit on the screen contents - or possibly on
what else is going on. Hiding the browser window makes it happen less,
I think. But I suspect that's about "less gpu activity" than anything
else.
I'll see if I can bisect it at least partially.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
"Koenig, Christian" <christian.koenig@amd.com>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Mon, 10 Jan 2022 17:21:09 -0800 [thread overview]
Message-ID: <CAHk-=wiCCRG9Lwzr+Cur=K1V2GJ9ab_ket7EnG4RZhJ8jJM7xQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_OYO7kq+9DBnDvbSfpouFvdLB0LPSL6+f1ZPRBsV=qEqA@mail.gmail.com>
On Mon, Jan 10, 2022 at 5:11 PM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> We are putting together a system to try and repro the issue. Does it
> happen with a single monitor or only with two?
Nope. With a single monitor everything seems to look fine. And when I
plug in the second monitor, it immediately starts happening again.
It also seems to depend a bit on the screen contents - or possibly on
what else is going on. Hiding the browser window makes it happen less,
I think. But I suspect that's about "less gpu activity" than anything
else.
I'll see if I can bisect it at least partially.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
"Wentland, Harry" <harry.wentland@amd.com>,
Dave Airlie <airlied@gmail.com>,
"Koenig, Christian" <christian.koenig@amd.com>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Mon, 10 Jan 2022 17:21:09 -0800 [thread overview]
Message-ID: <CAHk-=wiCCRG9Lwzr+Cur=K1V2GJ9ab_ket7EnG4RZhJ8jJM7xQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_OYO7kq+9DBnDvbSfpouFvdLB0LPSL6+f1ZPRBsV=qEqA@mail.gmail.com>
On Mon, Jan 10, 2022 at 5:11 PM Alex Deucher <alexdeucher@gmail.com> wrote:
>
> We are putting together a system to try and repro the issue. Does it
> happen with a single monitor or only with two?
Nope. With a single monitor everything seems to look fine. And when I
plug in the second monitor, it immediately starts happening again.
It also seems to depend a bit on the screen contents - or possibly on
what else is going on. Hiding the browser window makes it happen less,
I think. But I suspect that's about "less gpu activity" than anything
else.
I'll see if I can bisect it at least partially.
Linus
next prev parent reply other threads:[~2022-01-11 1:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 6:12 [git pull] drm for 5.17-rc1 (pre-merge window pull) Dave Airlie
2022-01-07 6:12 ` Dave Airlie
2022-01-07 10:37 ` Christian König
2022-01-07 10:37 ` Christian König
2022-01-10 21:10 ` Linus Torvalds
2022-01-10 21:27 ` pr-tracker-bot
2022-01-10 21:27 ` pr-tracker-bot
2022-01-10 21:30 ` Linus Torvalds
2022-01-10 22:04 ` Daniel Vetter
2022-01-10 22:04 ` Daniel Vetter
2022-01-10 22:04 ` Daniel Vetter
2022-01-10 22:13 ` Alex Deucher
2022-01-10 22:13 ` Alex Deucher
2022-01-10 22:13 ` Alex Deucher
2022-01-11 1:04 ` Linus Torvalds
2022-01-11 1:04 ` Linus Torvalds
2022-01-11 1:04 ` Linus Torvalds
2022-01-11 1:11 ` Alex Deucher
2022-01-11 1:11 ` Alex Deucher
2022-01-11 1:11 ` Alex Deucher
2022-01-11 1:21 ` Linus Torvalds [this message]
2022-01-11 1:21 ` Linus Torvalds
2022-01-11 1:21 ` Linus Torvalds
2022-01-11 1:28 ` Linus Torvalds
2022-01-11 1:28 ` Linus Torvalds
2022-01-11 1:28 ` Linus Torvalds
2022-01-11 2:22 ` Linus Torvalds
2022-01-11 2:22 ` Linus Torvalds
2022-01-11 2:22 ` Linus Torvalds
2022-01-11 2:44 ` Linus Torvalds
2022-01-11 2:44 ` Linus Torvalds
2022-01-11 2:44 ` Linus Torvalds
2022-01-11 2:52 ` Linus Torvalds
2022-01-11 2:52 ` Linus Torvalds
2022-01-11 2:52 ` Linus Torvalds
2022-01-11 15:08 ` Alex Deucher
2022-01-11 15:08 ` Alex Deucher
2022-01-11 15:08 ` Alex Deucher
2022-01-11 15:38 ` Harry Wentland
2022-01-11 15:38 ` Harry Wentland
2022-01-11 15:38 ` Harry Wentland
2022-01-11 20:51 ` Linus Torvalds
2022-01-11 20:51 ` Linus Torvalds
2022-01-11 20:51 ` Linus Torvalds
2022-01-12 15:36 ` Harry Wentland
2022-01-12 15:36 ` Harry Wentland
2022-01-12 15:36 ` Harry Wentland
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='CAHk-=wiCCRG9Lwzr+Cur=K1V2GJ9ab_ket7EnG4RZhJ8jJM7xQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@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.