[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9twUvRoVcWHhBH7yuDDVj8K8aM0APQ8Yx3cx19keLJP8Gg@mail.gmail.com>
Date: Thu, 4 Aug 2022 14:24:26 +1000
From: Dave Airlie <airlied@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 5.20/6.0
On Thu, 4 Aug 2022 at 14:02, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Wed, Aug 3, 2022 at 8:53 PM Dave Airlie <airlied@...il.com> wrote:
> >
> > > It works on my intel laptop, so it's amdgpu somewhere.
> >
> > I'll spin my ryzen up to see if I can reproduce, and test against the
> > drm-next pre-merge tree as well.
>
> So it's not my merge - I've had a bad result in the middle of the DRM
> history too.
>
> On a positive note, my arm64 machine works fine, but that's just using
> fbdev so ...
>
> But another datapoint to say that it's amdgpu-specific. Not that that
> was really in doubt.
I've reproduced it, I'll send you a revert pile when I confirm it is
the buddy allocator.
Dave.
Powered by blists - more mailing lists