All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Mon, 10 Jan 2022 13:30:41 -0800	[thread overview]
Message-ID: <CAHk-=wg9hDde_L3bK9tAfdJ4N=TJJ+SjO3ZDONqH5=bVoy_Mzg@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tz=_hRpQV1V3M-=KmVVEbr1K166qeb-ne64PHk9Sn-ozg@mail.gmail.com>

On Thu, Jan 6, 2022 at 10:12 PM Dave Airlie <airlied@gmail.com> wrote:
>
>   git://anongit.freedesktop.org/drm/drm tags/drm-next-2022-01-07

Gaah. I merged things and it built cleanly, and I pushed it out.

But then I actually *booted* it, and that's not pretty.

It *works", but it's almost unusable because of random scanline
flickering.  I'm not sure how to explain it, but it's as if there
wasn't quite enough bandwidth on the scan-out, so you get these lines
of noise and/or shifted output. They are temporary - so the
framebuffer contents themselves is not damaged (although I don't know
how the compositor works - maybe the problem happens before scanout).

This is on the same Radeon device:

   49:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7)

with dual 4k monitors.

Any idea?

                  Linus

  parent reply	other threads:[~2022-01-10 21:31 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  6:12 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 [this message]
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
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-=wg9hDde_L3bK9tAfdJ4N=TJJ+SjO3ZDONqH5=bVoy_Mzg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=Christian.Koenig@amd.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)' \
    /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

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.