[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKMK7uEag=v-g6ygHPcT-uQJJx+5KOh2ZRzC2QtM-MCjjW67TA@mail.gmail.com>
Date: Mon, 10 Jan 2022 23:04:46 +0100
From: Daniel Vetter <daniel.vetter@...ll.ch>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Alex Deucher <alexdeucher@...il.com>,
"Wentland, Harry" <harry.wentland@....com>
Cc: Dave Airlie <airlied@...il.com>,
"Koenig, Christian" <christian.koenig@....com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
On Mon, Jan 10, 2022 at 10:30 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Thu, Jan 6, 2022 at 10:12 PM Dave Airlie <airlied@...il.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?
Since Christian is mostly the compute/memory side, adding some display
folks for this.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists